All our aggregates are wrong
summary
Starts from a shopping cart example and argues the cart is not a single aggregate but a projection of multiple bounded contexts (sales, warehouse, shipping, marketing), showing concrete code sketches in C# and MVC Core and a client-side composition gateway that composes service responses into a view model. Uses queues and retries for writes, recommends the outbox pattern or transactional MSMQ over HTTP calls, explains eventual consistency, shows failures matter differently per component, and even notes 26 customer reviews as a motivating detail.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:10autonomy? poof, it's gone
- 16:40that's a cache
- 29:56things might go wrong
- 43:55there is no such thing as orchestration
related talks
50mDeveloping Microservices with Aggregates
57mSOA lessons learnt (OR Microservices done better)
38mMessaging Patterns to Transform Your Cloud Architecture
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
15mArchitecting Scalable Order Management Systems with Microservices
48mIT Architecture : All your micro-services are wrong PERIOD!
43mKey-Value, Event-Sourcing, Cqrs, Pub/Sub as a Service, Java, Javascript
36mDo Proper Monoliths before You Do Microservices!