APIs at Scale Through Minimalism in Code and Architecture
summary
Argues that the right goal is the least complex viable system not the simplest, showing how a single-instance app fails while a cluster with stateless instances behind a load balancer and DB nodes survives failure and scales. Calls out AWS autoscaling, warns about vendor lock‑in and “silver bullets,” and forbids shoehorning AI or blockchain. Recommends choosing languages and architecture for the workload (monoliths for small, microservices for true distribution) to get fault tolerance, scalable capacity and easier maintenance.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:55Morality
- 8:57Minimize
- 9:52Declutter
- 10:48Avoid vendor lockin
- 12:11Avoid solutions
- 13:38Use the right tools
- 16:01Benefits
related talks
49mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
36mOne to millions - opportunities and challenges in scaling APIs.
26mArchitecting for scale
38mSimplicity: The Key to Software Success
34mArchitektury Aplikacji: The last mile of microservices
30mBowerbirds of Technology: Architecture and Teams at Less-than-Google Scale
23mSearching for scale through API's
32mA Simpler Time: Balancing Simplicity and Complexity