Skip to main content

Detailed text description: Managed Container architecture

This page provides a long description of the architecture diagram used in the Managed Containers article.

Overview​

The diagram compares two runtime types operating within the same landscape:

  1. Reactives.
  2. Managed Containers.

Main components and relationships​

  1. Router:
  • Positioned at the top.
  • Routes traffic to both runtime types.
  1. Reactive Service (left side):
  • Runs on a Codesphere-provided base image.
  • Uses the platform default runtime model.
  1. Managed Container (right side):
  • Runs a custom OCI image.
  • Receives image artifacts from an external public registry.
  1. Public Registry to Managed Container flow:
  • A dashed arrow indicates image pull behavior.
  • This denotes that the platform pulls the custom image from an external registry source.
  1. Codesphere agent injection:
  • Inside the managed container, the Codesphere agent is present under /home/user/app.
  • This enables platform integration features.

Key takeaway​

Both Reactives and Managed Containers are shown within the same landscape boundary. They share orchestration, networking, and core platform capabilities, while differing primarily in image source and customization model.