Ticketing Platform - Architecture Diagrams
AWS infrastructure, service view, data ownership, the reservation and payment saga,
web and MCP authentication, the virtual waiting room and search. Generated from source
(docs/diagrams/*.py) and kept in sync with the code.
1 · AWS Infrastructure
Reference production architecture on EKS: VPC, MSK, RDS Multi-AZ, ElastiCache, Kong, edge services, observability, IRSA.
AWS icons2 · AWS Architecture (service view)
Edge, VPC and EKS services grouped by domain (Identity, Catalog, Transaction), with REST, gRPC, GraphQL Federation and Kafka flows on one page.
AWS icons3 · Data Model
Per-service database ownership. Dotted lines mark logical cross-service references (no enforced foreign keys).
C44 · C4 Container
Service topology and protocols.
Sequence5 · Data Flow / Saga
Reservation, payment, finalize and expire flow with CloudEvents on MSK, transactional outbox and DLQ.
Sequence6 · Auth Flows (web)
Browser sign-in, refresh rotation with family revocation, internal gRPC trust and the Stripe webhook; RS256 JWTs verified at Kong.
Sequence7 · MCP Auth Flows
How an MCP agent gets access: OAuth 2.1 + PKCE, client metadata document (CIMD) or dynamic registration, consent, audience-bound tokens, per-call token exchange, scope step-up, revocation.
Sequence8 · Virtual Waiting Room
Onsale surge gate: pre-queue fair draw, rate-based admission, single-use HMAC pass, clean-URL redemption.
Sequence9 · Search Dataflow
OpenSearch CQRS read model: Kafka-fed index path and the ranked query path with live Mongo hydration and regex fallback.