Autonomous microservices don't share data. Period.
summary
Claim: true autonomy requires services to own and not share business data; containers or .NET Core don't fix coupling. Achieve this with fine-grained events that carry identifiers only, e.g. order accepted (orderId only) and follow eventual consistency, not by duplicating whole records. Front ends become a composite UI that assembles per-service views. Partition around consistency needs — for example price vs discount consistency boundary — and prefer publish/subscribe events and local state over cross-service data queries.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:13Monoliths to microservices
- 8:00Layered architectures fail
- 14:08Microservices rise and pitfalls
- 23:06Shared data breaks autonomy
- 29:48Correct service boundaries
- 37:12Autonomous services design
- 42:03Event-driven architecture
- 47:05Event sourcing pitfalls
- 50:32Autonomous microservices don't share data
related talks
43mAutonomous microservices don't share data
47mAutonomous Microservices Don't Share Data. Period
01h 00mPrinciples for Building MicroServices
39mManaging Consistency, State and Identity in Distributed Microservices
27mData Consistency in Microservices Architecture
43mData Access and Data Sharing in Microservices
53mData Access and Data Sharing in Microservices
01h 01mArchitectural Principles and Practices to Build MicroServices