Discord Bot Platform  ·  View 02 of 19  ·  Context and scope

High-Level Architecture

Left to right: commit, entitle, route, deliver. The event is filtered before it is serialised.

Editable source SVG draw.io All views
Chat service Commit Events per-server stream Fan-out Entitlement Filter intents x permissions Server Partitions Event Hubs Sessions Gateway Shards AKS stateful pods Session & Resume Azure Cache for Redis Edge WebSocket Edge Front Door + L4 API Edge auth, rate limit Bots Bot Processes Interaction Endpoints resume buffer actions Discord Bot Platform — High-Level Architecture Queue / topic Application we own Data store Interface / broker External / third party event / async synchronous Control plane (registry, installs, commands, tokens) is drawn in view 06. v 1.0 · owner Integration Platform Architecture · date 2026-10

Why it reads this way

  • Events flow one way into bots. Bot actions return through the API edge, never through the event path (ADR-01).
  • The filter sits before the shard, so bytes a bot may not see are never produced (ADR-02).
  • The resume buffer is the only per-session state on the path, and it is bounded (ADR-04).

Omitted

  • Control plane, registry and commands (view 06), to keep the event path legible.
◀  System Context All views Actors and Core Journeys  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records02-high-level-architecture