📄️ Container Orchestration
Each service of the real-time architecture forms a self-contained deployment unit. To do this, each service is encapsulated in its own container with its dependencies, such as the required libraries. The advantage of this is the simplified deployment, because all dependencies of the software encapsulated in the containers are delivered with a software container. This makes it possible to always deploy a service in the same way in production on any system and no dependencies, for example on software versions, have to be taken into account.
📄️ DetOrchestration
The figure provides an overview of the key information that the software components involved in real-time orchestration require. The lifecycle of a distributed real-time system (DRTApp) begins with a description of the execution model used and the composition of the DRTApp from individual services (containers). Subsequently, a scheduler, which can be integrated either into a real-time orchestrator or an external tool, assigns scheduling parameters to the services encapsulated in containers. To draw conclusions about the real-time behaviour of the DRTApp to be deployed, specific validators and user-defined validators associated with the scheduling model are used. Finally, service configuration files and deployment descriptions are generated for the runtime environment of a specific type of deployment unit.