Skip to content

C4 model

C4 is Context, Containers, Components, and Code. We maintain a LikeC4 model under /c4 (ADR 0003). Mermaid stays on the infra pages for sequences; LikeC4 is the navigable topology.

Open interactive diagrams (use this)

bash
npm run c4:dev        # interactive UI with live reload
npm run c4:validate   # CI gate
npm run build         # export into docs site + VitePress

Views

Product (apps)

ViewQuestion
System contextWho uses FalconX? What is outside (Betfair, bookmaker feeds)?
Containers (apps)Which EKS services, Lambda, Aurora, Valkey, MSK exist and how they talk
Money pathPlace-bet → User / Bets / settlement Lambda
Odds & catalogueStream vs poll into FrontMarket / Markets

Infrastructure (platform)

ViewQuestion
Infra — System contextUsers, GitHub, Groundcover, Sentry around FalconX
Infra — Request pathWAF → CloudFront → Traefik HTTPRoute → pod
Infra — Kubernetes computeKarpenter NodePools, Traefik, Argo CD, settlement Lambda
Infra — Data planeAurora + DA, Valkey, MSK, Debezium outbox, Secrets Manager
Infra — Ship pathGitHub Actions → ECR → Argo CD → pods
Infra — ObservabilitySensor → Groundcover; SDK → Sentry
Infra — AWS accountsDevelop+perf account vs prod account
Infra — Develop + perfShared VPC/EKS, two namespaces
Infra — ProductionDedicated VPC, cluster, data plane

Source files: c4/model.c4 (product) and c4/infra.c4 (platform, deployment).

We do not model the Code level — it would rot immediately.

Written walkthrough of the same platform: Infra · Visual map · Repos.

BigBash architecture SSOT — hosted for the team; edit via pull requests.