Finding Your Service Boundaries - a Practical Guide
summary
Argues that wrong service splits end up as a “big ball of mud” and gives concrete tactics that actually prevent that: model use cases with the pile method, ask anti-requirements to expose stable rules, prefer thin events (IDs only) and create the ID at the start of a workflow so services don’t share mutable data. Shows e‑commerce, hotel and insurance examples, explains tradeoffs (extra transient records vs. loose coupling), and claims these choices cut cross‑service coupling and deployment churn in practice.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 7:10From classes to big ball of mud
- 17:07What a service really is
- 24:46Modeling by behaviors not entities
- 33:19Breaking down insurance domains
- 37:12Organizational vs service boundaries
- 40:44Microservices pitfalls
- 46:44Physical vs logical separation
- 47:49Service boundaries in startups
- 49:13Q&A and closing remarks
related talks
58mFinding your service boundaries - a practical guide
49mFinding your service boundaries - a practical guide
58mFinding your service boundaries - a practical guide
26mDrawing the right lines: DDD, APIs and Microservices
54mServices, Services, Everywhere!
16mMicroservices Paradise: is it possible to achieve?
01h 01mCapability Mapping
56mDesigning in the World of Microservices