Why You Had a Bad Time With Microservices

on YouTube ↗23m

" summary

Argues microservices pay off well below “Google scale,” shows an HPC case where an API, message bus, event sourcing and CQRS replace a tightly coupled MVC monolith, yielding materialized read models, easier tests, faster onboarding, and new features (SMS) added without touching core logic. Demonstrates moving file jobs through events, using Elasticsearch for read views, and explains autonomy: services neither query nor depend on others, which is the practical success criterion.

AI-written summary · about

" chapters (11)

1. 0:00Intro
2. 0:21Software is hard to change
3. 2:51Whats the model
4. 5:40Extract Microservices
5. 8:13Autonomy
6. 9:23No Kittens
7. 10:03Commands and Events
8. 11:51Domain Events
9. 13:12Case Study
10. 17:58System Components
11. 21:15Summary

" related talks

• 54mThe Long Sad History of MicroservicesGreg Young · Build Stuff 2016
• 43mPanel: Microservices, Where Did It All Go WrongKris Jenkins, James Lewis, Ian Cooper · GOTO Copenhagen 2024
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016
• 44mMicroservices, Where Did It All Go WrongIan Cooper · GOTO Copenhagen 2024
• 50mChallenges in Implementing MicroservicesFred George · GOTO Copenhagen 2015
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017