Microservices: A Utopian Mystery

on YouTube ↗52m

" summary

Gives ten concrete lessons from a migration of a 20‑year C system to microservices, with actionable specifics: keep services small (rewritable in ~two weeks), package services as RPMs baked into AMIs and track RPM versions per story, use semantic versioning, tolerant readers and feature toggles to avoid breaking changes, ChatOps (Qbot), ELK/Kibana dashboards, Hystrix circuit breakers, health checks that include dependent services, contract + service + journey/soak tests, Chaos Monkey, and reorganize teams into vertical feature slices.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 9:04Keep it small
3. 13:11Focus on autonomy from design to deployment
4. 17:01Plan for contingency measures aka breaking changes
5. 22:48Pay attention to bounded context
6. 25:24Choose what works for you and document your reasons
7. 33:02Embrace Conway's Law
8. 36:29Take monitoring seriously
9. 40:31Testing; Do it.
10. 47:25Invest in infrastructure
11. 48:35Embrace new technology

" related talks

• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 57m6 Lessons I Learned on My Journey from Monolith to MicroservicesEran Stiller · .NET Fest 2019
• 43mGo micro with MicroservicesMariusz Gil · International PHP Conference Spring 2017
• 49mMicroservices: An unexpected JourneySam Newman · JavaDay Ukraine 2017
• 01h 03mThe Magic of Small Things - 10 Years of MicroservicesJames Lewis · GOTO Copenhagen 2024
• 36mMicroservices Lessons LearnedSusanne Kaiser · Voxxed Days Microservices 2018
• 01h 00mMicroservices, Where Did It All Go Wrong?Ian Cooper · NDC Melbourne 2025