Phase 10 · Production Problem → Solution
Senior-level incident scenarios and the architecture that fixes them.
- Incidents I: Slowness & Data-Layer Pain: War-room playbooks for slow systems: databases, connection pools, N+1, caches, Redis outages and a blocked Node event loop — symptoms, first 5 minutes, fixes, and the interview answer.
- Incidents II: Scale & Growth: Traffic 10× and 100×, hot servers and hot shards, read/write saturation, replication lag, sharding and zero-downtime migrations, global latency, static content, big uploads and millions of jobs
- Incidents III: Async, Dependencies & Resilience: Growing queues, slow and crashing consumers, duplicates, ordering, retries and retry storms, unavailable or slow downstreams, circuit breakers, cascading failures and noisy tenants
- Incidents IV: Correctness, Regions & Operability: Duplicate payments, races, deadlocks and locks; consistency choices; AZ and region failures, DR; sudden latency, bad deploys, tracing; slow and stale search
- Real-World Dissections: Famous Architectures & Outages, Explained: Twelve primary-source case studies (GitHub, Discord, Uber, Hotstar, Slack, Cloudflare, AWS, Meta, Figma, Notion), each told as context, timeline, root cause, what changed, lessons, and how to cite it in an interview
- Architecture Evolution Stories: Airbnb, Netflix & Shopify: Three companies hit the same growth wall and gave three different answers: layered SOA, cloud microservices behind a gateway, and a deliberately modular monolith split into pods. Each story is told stage by stage (trigger, constraint, decision, cost, lesson) from primary sources, then turned into a staged plan for a NestJS monolith