Skip to main content

Detailed text description: Managed services architecture

This page describes the managed services architecture diagram.

Overview​

The diagram illustrates a control-loop model connecting users, Codesphere control plane components, provider backends, and service infrastructure.

Main flow​

  1. User interaction:
  • A user requests service creation or updates through the Codesphere UI or API.
  1. Marketplace and internal state:
  • Codesphere stores desired service state, including plan, config, and secrets.
  • This desired state is maintained in the platform data model.
  1. Reconciler to backend communication:
  • Codesphere reconciles desired and actual state by communicating with managed service backends.
  • Backends report status and details back to Codesphere.
  1. Backend to infrastructure execution:
  • Backend implementations perform provisioning and lifecycle actions against underlying infrastructure.
  • Infrastructure can be internal cluster resources or external systems.

Core building blocks represented​

  1. Service Providers define service type and configuration contract.
  2. Provider Backends implement lifecycle operations.
  3. Service Infrastructure hosts the actual provisioned resources.

Key takeaway​

Codesphere acts as the orchestration control plane while provider backends execute infrastructure operations and continuously report status for reconciliation.