Detailed text description: Reactive runtime architecture
This page describes the reactive runtime architecture diagram.
Overview
The diagram shows how a reactive service runs on Codesphere orchestration with persistent storage and off-when-unused behavior.
Main components
- Incoming traffic path:
- Requests enter through platform routing.
- Traffic is forwarded to reactive service instances.
- Reactive service instances:
- Instances run as orchestrated workloads.
- Health checks and restart behavior are managed by the platform.
- Horizontal scaling can add multiple replicas.
- Shared filesystem:
- Service instances mount a shared network filesystem.
- Data in the mounted workspace path persists across restarts.
- Resource lifecycle:
- Active workloads consume compute while serving traffic.
- During idle periods, instances can be scaled down.
- On new traffic, instances are started again while persistent filesystem data remains available.
Key takeaway
The architecture combines managed orchestration, persistent shared storage, and demand-based compute usage for stateful application services.