Discord Bot Platform  ·  View 12 of 19  ·  Runtime

Event Fan-out Pipeline

Filter before serialise; shed at the session, never upstream.

Editable source SVG draw.io All views
Commit Chat Commit message.create Partition Server Partition key = server_id Entitle Installed Bots cached lease Intent Filter drop before serialise Route Shard Router id >> 22 mod N Deliver Gateway Shard per-session buffer Shed / Close slow consumer Bot Bot Socket entitled set buffer full Discord Bot Platform — Event Fan-out Pipeline External / third party Queue / topic Data store Decision point Application we own Risk / gap synchronous failure / alternate Hot-server handling (sampling presence, never moderation events) is a Phase 3 partition class. v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Partition by server so a hot server is one partition, not many copies (ADR-05).
  • A full session buffer closes that session with a resumable code; it never grows memory or blocks the shard (ADR-04).

Deferred

  • Dedicated partition class for 2-million-member servers is Phase 3.
◀  Critical Flow — Slash Command to Reply All views Critical Flow — Reconnect and Resume  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records12-event-fanout-pipeline