This repository aims to be the single source of truth about the architecture and the behavior of the FLUIDOS ecosystem. It will also be an indexing point for all the artifacts and repositories involved.
This is not intended as a project deliverable, but as a guidance for FLUIDOS partners to address the several activities to be carried out throughout the development.
The IT landscape has evolved into a world of hyperconnectivity, where devices and information systems communicate and exchange data on numerous applications. FLUIDOS will leverage the enormous, unused processing capacity at the edge, scattered across heterogeneous edge devices that struggle to integrate with each other and to form a seamless computing continuum coherently.
FLUIDOS architecture is made up of two main objects, very different from each other still greatly coupled in several workflows: the Node and the Catalog. While the first is mandatory, as it's the base element of the ecosystem, the latter is optional, and jumps in whenever there's the need to go cross-domain or let the general public access the ecosystem through a user interface.
-
Different type of workflow can be identified according to the presence of specific components in the scenario and the location of the involved nodes. The following workflows are described:
- Same domain scenario:
- Different domains scenario:
The FLUIDOS architecture is presented mostly in a technology-agnostic fashion. All technology-dependent and implementation related details are addressed in deliverables provided by the following main activities:
- FLUIDOS Node Implementation
- Intent-based Computing Continuum
- Security
- Energy and Cost-effective Infrastructure
The FLUIDOS project is under the Apache 2.0 license. Please see details here.