Discord Bot Platform  ·  View 09 of 19  ·  Data

Data Architecture and Storage Zones

Four zones, classed by how they can be lost.

Editable source SVG draw.io All views
Zone 1 — Registry (strong, small, never lost) Cosmos DB, multi-region writes off Applications Installations & Grants Commands Token Hashes Zone 2 — Session (rebuildable by reconnecting) Redis + in-pod memory Session Records Resume Buffers 120 s / 5k events Zone 3 — Counters (approximate, regional) Redis cluster per region Rate-limit Buckets Identify Quotas Zone 4 — Evidence (append-only) Blob + Log Analytics API Audit, 90 days Security Events, 13 months Discord Bot Platform — Data Architecture and Storage Zones Message content is never stored here. Zones 2 and 3 are rebuilt, not restored. v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Registry loss is a defect (RPO 0). Session loss is a reconnect. Counter loss is a brief over-allowance (ADR-10).
  • Evidence is append-only and outlives the bodies it describes.

Risk

  • Redis failover resets the sessions of a region's bots at once; the identify throttle is what keeps the registry alive.
◀  Interface Catalogue All views Data Model  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records09-storage-zones