From Macro To Micro
summary
Explains how to split a monolith by mapping bounded contexts to services, using package visualization tools like Structure101 and DB tools like schema spy, then moving to separate schemas so catalog, finance, ledger, customer and inventory become independent services; recommends starting coarse and iterating, watching operability (one service per host, cloud provisioning, monitoring), uses the heuristic of ~200 lines of code per simple service, and reports that incremental refactoring reduces risk and enables safe experimentation.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:30Breaking Apart Systems
- 3:50What is a Good Service
- 6:50Physical Delivery of Media
- 14:00Packages
- 15:40Databases
- 20:40AFI
- 22:54Journey of Discovery
- 27:27Rules of UNIX
- 35:01How small should I go
- 37:24How big should I go
- 41:31Summary
- 43:47Questions
related talks
48mExperiences scaling a modular monolith to microservices using the 4+1 views
37mEvolutionary Architecture & Microservices
59mDecomposition Patterns
42mQ&A - Monolith to Microservices
01h 03mFrom Monolith to Microservices: Story and Practice
48mModel Mitosis: Stop Confusing Microservices and the Monolith
38mFrom Monolith to Microservices
46mFrom microservices to migroservices