Skip to main content

Deployment Topology

:::info Source Sourced from services/catalog-service/DEPLOYMENT_TOPOLOGY.md in the documentation repo. :::

1. Containers​

  • catalog-api — REST API (browse, courses, taxonomies).
  • catalog-worker — event-driven projections + outbox relay.

2. Scaling​

ContainerMinMaxHPA
api320CPU>60%
worker28queue depth > 100

3. Resources​

api: 500m/2000m, 512Mi/1.5Gi. worker: 300m/1500m, 256Mi/1Gi.

4. Caching​

  • Redis: course detail cache (5 min), taxonomy tree cache (60 min).
  • CDN: public catalog listing pages (5 min); purged on publish/withdraw.

5. Regional​

  • Per region. Catalog is mostly read-heavy; replicate via projections.

6. Service Mesh​

mTLS. Egress: search-service, marketplace, authoring, content, analytics.

7. Release​

Blue/green. Migrations fwd+back.

8. DR​

RPO 5 min. Catalog rebuildable from event log.