Runtime Fabric architecture on EKS

Let’s take a look at the Runtime Fabric on self-managed Kubernetes architecture. This architecture and how its many components interact and coordinate are shown in the following figure:

Figure 11.12 - Runtime Fabric architecture on EKS (self-managed Kubernetes)

Figure 11.12 shows various components and how they interact with each other:

• The Persistence Gateway is responsible for storing object store data in a persistent data store. The application must be clustered to share the data, such as in an object store or VM queues across the replicas. The Persistence Gateway will ensure that this data doesn’t vanish if the application restarts or is deployed and recovers from any crashes.
• The Docker Pod is the worker node that’s responsible for pulling the specific version of the Mule runtime from the Mule Docker registry.
• The log forwarder agent will forward logs to external systems, such...