Granularity & Communication for Microservice Architectures
summary
Provides concrete rules: use five disintegrators (functionality, volatility, scalability/throughput, reliability, security) and three integrators (transactions, data ownership, workflow) to iterate service boundaries; evaluates eight saga variants (synchronous vs async, atomic vs eventual, orchestration vs choreography) with clear failure modes — the horror story pattern (async+atomic+choreography) is an anti‑pattern. Shows practical fixes like transactional sharding (one service per seat section) that achieves transactional behavior without distributed transactions.
AI-written summary · about
chapters (6)
- 0:00Introduction to coupling
- 2:57Service granularity tools
- 9:45Integrators for services
- 17:01Dynamics of workflows
- 30:44Transactional sagas
- 57:18Conclusion
related talks
46mGranularity & Communication for Microservices Architectures
44mGranularity and Communication in Microservice Architectures
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
40mCAPtivating architecture: Navigating Distributed Systems and Microservices
50mTransactional solutions for microservices
58mImplementing Event-driven Microservices
24mPatterns of Evolution from Monolith to Microservices
27mThe technical journey to microservices