SOA lessons learnt OR Microservices done better
summary
Tells a concrete failure: splitting a monolith into multiple web services causes cascading slowdowns and service denial, so synchronous calls between services become the root problem. Recommends carving bounded contexts, owning write data (never share writes), favouring asynchronous communication with durable queues (NServiceBus on .NET is named), apply CQRS for reads vs commands, keep vertical slices thin, name intentful commands not generic CRUD, automate deploys and add monitoring. Key lessons: temporal coupling, do not share writes, use durable queues
AI-written summary · about
chapters (5)
- 0:00The challenges of monoliths
- 9:22The root cause: Coupling
- 9:43Understanding coupling
- 22:38Microservices paradigm
- 24:04Best practices for success
related talks
57mSOA lessons learnt (OR Microservices done better)
01h 00mService Oriented Architecture for Robust & Scalable Systems
23mWhy You Had a Bad Time With Microservices
45mBuilding and evolving microservices: lessons from the frontlines
36mDo Proper Monoliths before You Do Microservices!
38mMicroservices, a bittersweet symphony
40mSOD Microservices - Daniel Jones, EngineerBetter
50mEmbracing Microservices