Autonomous Microservices Don't Share Data. Period
summary
Microservices should never share domain data; instead they communicate using events (e.g., orderSubmitted, paymentCompleted) and only pass identifiers. The talk demonstrates an order flow where independent services compute prices, discounts and shipping from their own data stores, using messaging and Docker containers for deployment and communication to avoid distributed-monolith coupling.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 6:30Monoliths to components
- 9:42Web services hype cycle
- 12:12Microservices vs smaller services
- 16:50Shared data dangers
- 21:48Encapsulation and autonomy
- 26:48Identifiers over shared data
- 33:21Logical component breakdown
- 34:46Event-driven autonomy
- 44:33Reclaiming SOA core
- 46:59Q&A
related talks
43mAutonomous microservices don't share data
53mAutonomous microservices don't share data. Period.
01h 00mPrinciples for Building MicroServices
43mData Access and Data Sharing in Microservices
44mA Software Engineer's Journey Through Microservices Data Sharing
18mMicroservices Architecture: Design Principles & Best Practices
49mMicroservices: An unexpected Journey
01h 01mArchitectural Principles and Practices to Build MicroServices
