Effective Microservice Communication and Conversation Patterns
summary
Uses real-world restaurant metaphors to map concrete patterns: initial customer interaction uses HTTP synchronous request-response with a claim check (202 Accepted) for fast acknowledgement; simple durable queues implement a routing slip (bag with circled items) for FIFO work and temporal decoupling; complex orders use pub/sub events plus an observing process manager (choreography) or a central command process (orchestration) to coordinate steps. Example math: 2.5 minutes per order → ~24 orders/hour; parallelized workers raise capacity to ~120 orders/hour.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 2:30Jimmy Bogard
- 4:26Microservice definition
- 7:59Real life examples
- 13:17Business model example
- 14:24Waiting in queues
- 17:41Hiring more workers
- 20:31How do we process individual orders
- 22:05Placing an order
- 24:31HTTP
- 25:21Conversation Patterns
- 25:55The Backend
- 26:40Demo
- 27:40Service unavailable
- 29:08Fire and forget
- 30:25Mighty Find
- 31:32Routing Slip
- 37:58Process
- 41:57Choreography
- 43:38Larger Restaurants
- 44:24Large Restaurants
- 45:00synchronous interaction
- 45:18orchestration
- 47:40orchestration vs choreography
- 48:43wrap up
- 49:28more resources
related talks
59mEffective Microservice Communication and Conversation Patterns
53mEffective Microservice Communication and Conversation Patterns
48mIntegration- and conversation-patterns for microservices
52mSo You Want to Build An Event Driven System?
54mEfficient Microservice Communication
18mMicroservices Architecture: Design Principles & Best Practices
15mArchitecting Scalable Order Management Systems with Microservices
24mPatterns of Evolution from Monolith to Microservices