Top 5 techniques for building the worst microservice system ever
summary
Shows five concrete anti-patterns that reliably wreck microservices: using Strangler fig extraction to create a networked monolith with .NET Gen2 garbage‑collection pauses; replacing sync calls with queues and endless retries then a dead‑letter queue that needs manual tooling; doing a big‑bang rewrite that doubles production systems; reinventing frameworks instead of using NServiceBus/off‑the‑shelf libraries; and splitting noun‑based services (product/order/customer) then patching with an engine pattern of shipped DLLs — all built examples and why each fails.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:26Who is William and his background
- 5:16Microservices done wrong
- 8:28Strangler fig pattern misuse
- 16:39Big bang rewrite failures
- 24:43Reinventing wheels with frameworks
- 29:00Service boundaries with nouns
- 34:15Logical vs physical boundaries
- 43:00Q&A
related talks
41mTop 5 techniques for building the worst microservice system ever
40m10 tips for failing at microservices
30mHow to Fail at Building Modern Microservices
39m10 Tips for failing at microservices
57mEmbracing Microservices
47mEmbracing Microservices
50mThe Seven Deadly Sins of Microservices
01h 00mMicroservices, Where Did It All Go Wrong?