Designing and Testing Resilient APIs for India Scale
summary
Eight concrete patterns for India-scale APIs: a local-first POS that runs offline and uses isomorphic modules (JavaScript/WebAssembly npm packages) to avoid duplicated validation; a telco rating path handling 60,000 RPS / 300 ms using a cell-based deployment and a loop back to Kafka (queue-and-reconcile) when SLAs approach breach; shift critical sync APIs to async and durable workflow tools (Temporal) for elasticity of time; generative/spec-driven resilience tests find only 4 of 200 MCP servers passed real fault injection.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:28Local first design POS
- 6:45Cell-based telecom architecture
- 9:35Loop back charging pattern
- 12:03Shadow mode testing
- 13:48Async paths in e-commerce
- 15:38Durable workflows
- 17:08Load shedding for ticketing
- 19:19Resiliency testing MCP
- 20:24Q&A
related talks
01h 31mFive Design Patterns to build resilient Applications
44mArchitectural Patterns of Resilient Distributed Systems
24mDesigning the APIs for an Internal Set of Services
18mScaling APIs to Billions: Extreme-Scale Reliability
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
56mArchitecting Cloud Native Microservices
25mResilience testing in modernization projects
37mAPI Horror Stories from an Unnamed Coworking Company