Finding your service boundaries - a practical guide
summary
Using the Amazon order example he demonstrates creating the order ID at checkout (even client‑side), pushing address/payment fragments to Finance and Shipping during the workflow, and finally publishing an event with just an ID. This keeps events thin, avoids fat payloads that force simultaneous deployments, and cuts coupling so services only need the order ID to proceed. He warns microservice sprawl produces a distributed big ball of mud and notes abandoned checkout data can be valuable for analytics.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:45Systems
- 5:50Classes
- 9:42Amazon
- 11:20Amazon backend
- 19:00What is a service
- 24:09Concrete example
- 24:45Anti requirements
- 30:47Insurance
- 37:01Organizations
- 40:34Microservices
- 44:26Logical services
related talks
49mFinding your service boundaries - a practical guide
58mFinding your service boundaries - a practical guide
50mFinding Your Service Boundaries - a Practical Guide
47mGetting (service) design right
58mDesign more decoupled services with one weird trick
52mSo You Want to Build An Event Driven System?
47mAutonomous Microservices Don't Share Data. Period
15mArchitecting Scalable Order Management Systems with Microservices