Communication Patterns in Microservices
summary
Introduces the architecture quantum as an independently deployable unit with high cohesion and a synchronous/asynchronous coupling metric called quantum kinescence, uses static vs dynamic kinescence to judge coupling, and shows a concrete latency example (50ms + 1700ms + 50ms = 1800ms) to illustrate synchronous entanglement. Recommends modeling synchronous vs asynchronous lines on base diagrams, using consumer-driven contract fitness functions and tools like Pacted to validate loose, versionless APIs.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:55Architecture quantum concept
- 4:43Coupling in software architecture
- 14:00Quantum kinescence explained
- 18:35Synchronous vs asynchronous calls
- 29:58Contract types and trade-offs
- 40:56Consumer-driven contracts
- 44:52Versioning strategies
- 49:45Making architecture decisions
related talks
44mGranularity and Communication in Microservice Architectures
48mIntegration- and conversation-patterns for microservices
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
54mEfficient Microservice Communication
59mEffective Microservice Communication and Conversation Patterns
38mMicroservices, a bittersweet symphony
51mEffective Microservice Communication and Conversation Patterns
27mApplication Integration Patterns for Microservices