Building Systems that Last
summary
Amazon documents a concrete evolution: a monolith becomes service orientation, then 70% key value, 20% single‑table, 10% relational drives DynamoDB and specialized databases; internal infrastructure-as-a-service automates capacity and databases so teams stop hoarding resources; S3 launches with 8 → 300+ microservices and evolves live via erasure coding and Glacier without downtime; reliability uses cell-based routing and overlapping shards so one failure only affects ~3.6% in an example; Rust adoption cuts CPU/energy costs versus Python/Ruby and cost metrics live on developer dashboards.
AI-written summary · about
chapters (8)
- 0:00Amazon Origins
- 3:02Classic Architecture
- 9:57Service Orientation
- 12:48Microservices Shift
- 14:38Cloud and AWS
- 21:37Reliability Strategies
- 27:27Cost and Efficiency
- 33:54Conclusion
related talks
31mPast, Present and Future of Microservices
37mBuilding Modern Distributed Systems with AWS
24mBuild modern applications with purpose-built AWS databases
25mFrom Millions of Customers to Petabytes of Data: A Journey to Microservices
33mPredicting the Future of Distributed Systems
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
40mBeyond Relational: Data storage for modern applications
25mBuilding Modern Applications with Custom Databases