Identifying and Scoping Microservices

on YouTube ↗49m

" summary

Three concrete rules decide microservice boundaries: make the primary cut by business capabilities (discover bounded contexts and map capabilities like points, eligibility, cards), use technical capabilities as a distant second (isolate notification gateways, push/email/SMS integrations), and shape scopes to respect team structure so developers work efficiently. Services own their data, deploy independently, and favor event-based collaboration. Fixes: merge services that always deploy together or split by sub-capability and data migration; when unsure pick slightly larger.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 1:14Microservices
3. 3:27Example
4. 5:26Why Microservices
5. 8:52Complexity
6. 11:10Characteristics
7. 14:26Bounded Context
8. 22:45Technical Bait Capabilities
9. 27:11Conways Law
10. 33:38Microservice Size
11. 36:25Microservice Splitting
12. 38:51Splitting Microservices
13. 40:53Summary

" related talks

• 45mResponsible MicroservicesNathaniel Schutta · Voxxed Days Microservices 2019
• 01h 00mPrinciples for Building MicroServicesVenkat Subramaniam · Developer Summit 2020
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 01h 02mDesigning MicroservicesVenkat Subramaniam · Great International Developer Summit 2025
• 26mCreating a scalable ecosystem of MicroservicesArchanaa Ravikumar, Pooja Subramanian · Apidays LIVE Paris 2020
• 55mCapability MappingIan Cooper · NDC Oslo 2020
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017
• 52mWhat Does a Good Microservice Architecture Look Like?Carola Lilienthal · JCON-ONLINE 2021