Past, Present and Future of Microservices
summary
HTTP and JSON become the default contract, enabling lightweight services and serverless & AWS Lambda deployments (first million invocations free); Amazon S3 starts as eight microservices and scales into 200+ supporting services, hitting trillions of objects and irregular peaks; retail systems architect visualizes hundreds of service dependencies and records 45 million requests/sec on DynamoDB during Prime events. Key problems are discoverability and observability (logs, metrics, tracing), plus practices like feature flags, game days and “you build it, you run it.”
AI-written summary · about
chapters (10)
- 0:00Start
- 6:53Micro-Service Architecture
- 12:15Amazon S3
- 16:48Security
- 18:22Identities
- 19:13Observability
- 19:49Distributed System Observability
- 22:01The Game Day
- 22:47Human Factor
- 29:02Recap
related talks
23mMicroservices – Diptanu Choudhury
45mMicroservices: A retrospective
49mChallenges in Implementing Microservices
01h 03mThe Magic of Small Things - 10 Years of Microservices
35mBuilding Systems that Last
54mThe Long Sad History of Microservices
39mBuilding Highly Scalable Microservices with Serverless
44mMicroservices, Where Did It All Go Wrong