Arrested Development
summary
Yelp’s Transaction Platform breaks a 1.2 million line monolith into many services and shows what actually goes wrong: initial wins in deployment speed give way to API creep and tangled coupling, tests that don’t cover distributed failure modes, and surprising operational bugs (one datacenter’s timings are ten times worse, causing partner 504s). Concrete fixes include Swagger specs plus bravado and pyramid Swagger for client/server validation, comprehensive logging into the ELK stack, and last_alert for actionable monitoring and alerts.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:38About Scott
- 3:14Microservices vs Monolith
- 5:25Monolith Decoupling
- 9:13Problems with Microservices
- 10:57Outline
- 11:27Python monoliths
- 13:26Swagger
- 16:13Swagger Automation
- 18:23Lessons
- 19:37Understanding Systems
- 21:25The ELK Stack
- 23:38How Does This Help
- 24:46Flexible Alerting
- 25:39Lessons Learned
- 26:33Summary
- 28:26Questions
related talks
42mArrested Development: surviving the awkward adolescence of a microservices-based application
43mBreak Up the Monolith: Testing Microservices
38mBuilding mobile APIs with services at Yelp
37mAPI Horror Stories from an Unnamed Coworking Company
54mAdrian’s Greatest Hits, B-Sides & Re-issues
47mBreak Up the Monolith: Testing Microservices
54mServices, Services, Everywhere!
30mMonolith to Microservices
