Example architectures12

Whole systems: their parts, how they talk, and what must stay true. Study one, then copy it and practise on your version.

Subscription SaaS
2,000 paying teams; 30 req/s at peak
SaaS8 parts
Course marketplace
40k students, 1,200 instructors, 5 purchases/min
Marketplace10 parts
Team chat
300k daily users, 2k messages/s peak, 1.5M open sockets
Realtime10 parts
Online store
50k orders/day, 20x spikes on sale days.
Commerce12 parts
Model inference API
400 customers, 300 req/s, p95 under 800 ms for small inputs
ML serving12 parts
Device telemetry platform
20k readings/s sustained, 13 months retention
IoT13 parts
Ride hailing dispatch
50k active drivers pinging every 4 s; 300 trip requests/s at peak
Mobility14 parts
Headless CMS and publication site
30 editors; 2M page views/day; 95% CDN hit rate
Content10 parts
Multiplayer game backend
60k concurrent players, 6k matches running, 30 ticks/s per match
Gaming12 parts
Wallet and payments ledger
1.5M wallets; 80 transfers/s at peak; daily settlement files
Fintech13 parts
Concert ticketing
100k buyers in the first minute of an on-sale; 20k seats per show
Ticketing12 parts
Hosted CI service
8k pipelines/hour; 600 concurrent runners
Developer tools11 parts