Finding your service boundaries - a practical guide
summary
Argues that service boundaries must follow business capabilities not entity models, using concrete patterns: generate an order/booking ID at checkout so services exchange IDs not data, apply anti-requirements to discover which fields truly belong together, and treat events as thin notifications to avoid coupling. Shows hotel and e-commerce workflows where copying price or customer data causes sprawl, warns microservices can create a distributed big‑ball‑of‑mud, and cautions startups against premature splitting.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 6:05Drawing a bunch of boxes
- 6:52A big ball of mud
- 7:26Tight coupling
- 9:09Spaghetti model
- 9:20Big ball of mud
- 10:05Amazon workflow
- 10:19Shipping address
- 10:53Events
- 15:11Checkout
- 15:21Shipping
- 18:00Sharing data
- 18:28What are services
- 20:03Systems vs services
- 21:51Anti requirements
- 23:40Finding service boundaries
- 26:27Naming
- 28:19Hotel
- 28:45Room type
- 29:34Dates
- 30:39Price
- 31:08Luxury
- 31:23Pricing
- 31:40Price per night
- 31:51False advertising
- 32:29Creating a booking ID
- 33:36Pricing options
- 33:51Business abstractions
- 34:37Booking your room
- 37:40Insurance
- 43:24Organizational boundaries
- 46:53Microservices
- 48:54Drawing microservices
- 49:43Autonomous components
- 51:47Microservice
- 53:22Video package
- 53:54Wrap up
related talks
49mFinding your service boundaries - a practical guide
50mFinding Your Service Boundaries - a Practical Guide
58mFinding your service boundaries - a practical guide
16mMicroservices Paradise: is it possible to achieve?
01h 01mCapability Mapping
49mIdentifying and Scoping Microservices
26mDrawing the right lines: DDD, APIs and Microservices
56mDesigning in the World of Microservices