Top 5 techniques for building the worst microservice system ever
summary
Five concrete antipatterns and their painful consequences: converting a monolith to many HTTP services on .NET causes more threads to linger and Gen2 stop-the-world pauses that collapse throughput; replacing sync calls with queues without idempotency or backoff explodes into lost payments and a clogged dead-letter queue; attempting a big‑bang rewrite usually stalls unless the system is tiny or it’s for a CV; rebuilding every framework (Polly, Rebus, NServiceBus alternatives) breeds not-invented-here work; splitting by nouns forces chatty cross-service calls unless you accept DLL/NuGet plugin engines.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:30Who am I
- 1:37Writing bad systems
- 4:20Why microservices
- 6:17Strangler fig pattern
- 12:08Network topology coupling
- 12:55Big bang rewrites
- 17:20Cut the rewrite
- 19:08Big bang rewrite
- 20:25Make it worse
- 23:37Not invented here
- 24:31Search screen
- 28:31Why is this not working
- 30:29Building a new monolith
- 34:39The engine pattern
- 39:26Recap
related talks
46mTop 5 techniques for building the worst microservice system ever
40m10 tips for failing at microservices
57mEmbracing Microservices
30mHow to Fail at Building Modern Microservices
47mEmbracing Microservices
01h 00mMicroservices, Where Did It All Go Wrong?
55mMicroservices, Where Did It All Go Wrong
53mDon’t Build a Distributed Monolith: How to Avoid Doing Microservices Wrong