Discord Bot Platform  ·  View 14 of 19  ·  Operations

Deployment Architecture

Each region is primary for its own shards and standby for a neighbour's.

Editable source SVG draw.io All views
Azure — Region A (primary for its shards) Edge Front Door WAF, TLS L4 Load Balancer WebSocket AKS — gateway pool (zones 1–3) Gateway pods StatefulSet Fan-out workers API pods stateless State Azure Cache for Redis Event Hubs Cosmos DB Key Vault Azure — Region B (standby for A, primary for its own) Mirror stack Gateway pods Event Hubs Cosmos DB replica Egress Pool NAT, published range HTTPS WSS replicate Discord Bot Platform — Deployment Architecture Application we own Data store Queue / topic Security / platform Interface / broker synchronous batch v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Registry replicates; sessions do not. A regional loss costs reconnects, not data (ADR-10).
  • Egress is a separate pool with a published range so bot allowlists keep working (ADR-11).

Assumption

  • RTO 5 minutes for new sessions, stated assumption.
◀  Critical Flow — Reconnect and Resume All views Release and Environments  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records14-deployment-architecture