3 reasons why micro-services aren't the miracle cure

on YouTube ↗20m

" summary

Argues microservices often trade one set of problems for another: one team ends up with 7–8 Cloud Run services that duplicate framework, pipeline and infra-as-code work; Spring’s Kafka integration forces repeated listeners; a single new feature (washing-machine installation) touches checkout, product page, invoice, carrier, accounting and analytics so deployment spans many teams and slows releases. Recommends practical mitigations like Spring Kafka integration abstractions, consumer-driven contracts and feature toggles, and warns architecture and org design must change too.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 2:58Microservices as problematic roommate
3. 7:51Repeating same problems
4. 9:37Microservices not simpler
5. 13:11New features not faster
6. 17:05Microservices not all bad
7. 18:52Summary

" related talks

• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016
• 49mChallenges in Implementing MicroservicesFred George · GOTO Amsterdam 2015
• 50mChallenges in Implementing MicroservicesFred George · GOTO Copenhagen 2015
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 44mMicroservices, Where Did It All Go WrongIan Cooper · GOTO Copenhagen 2024
• 42mMicroservices are Not Worth the Trouble!!??James Birnie · Agile on the Beach 2018
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017
• 55mMicroservices, Where Did It All Go WrongIan Cooper · NDC London 2025