3 Years Of Getting It Mostly Right
summary
Three years of micro‑service work at Tes.com yields concrete outcomes: roughly 137 services, small engineering teams of 3–4 people who deploy with Docker and Jenkins and push to production within days, about 50–60 releases a day, RabbitMQ for async messaging, DataDog for metrics, and an in‑house tool Boscoe to run the service catalog locally. The business wins faster launches and global scale; the costs are version sprawl, long‑lived services and ongoing tech‑debt tradeoffs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:08How we got here
- 4:32Whats a team
- 5:35Architecture
- 9:02Engineering
- 10:42First impressions
- 11:48Onboarding
- 13:19Service Catalog
- 14:22Consistency
- 15:52Service Catalogue
- 16:57Consistency Champion
- 19:46Maintenance Burden
- 20:52Where We Get Things Wrong
related talks
01h 01mMicroservices Gone Wrong
48mThirty months of microservices
23mOn the road from Monolith to Micro
35mSeven years with microservices: a critical review
35mTaming a beast
30mOur Continuous Delivery Journey
41mMe, My Organization and My-croservices
45mDesigning, building, testing and deploying microservices