Decomposition Patterns

on YouTube ↗59m

" summary

Eight concrete refactorings turn a monolith into a controlled service architecture: identify and size components, flatten root namespaces to eliminate orphaned classes, map component dependencies with tools like x-ray and SonarGraph and measure feasibility (example: 57 components, 23 in .shared; one component held 33% of code). Workflow: create component domains, extract to separate projects, deploy domain services, then selectively convert to microservices. Real results: some migrations finish as service-based architecture, others become multi‑year rewrites when dependency graphs look like a ball of yarn.

AI-written summary · about

" chapters (8)

1. 0:00Introduction to decomposition
2. 4:00Identifying and sizing components
3. 15:01Flattening component hierarchy
4. 30:37Analyzing component dependencies
5. 41:50Forming component domains
6. 45:02Extracting domain services
7. 47:29Moving to microservices
8. 57:31Summary and Q&A

" related talks

• 23mArchitecture RemediationShankar Ramakrishnan · Developer Summit 2020
• 52mWhat Does a Good Microservice Architecture Look Like?Carola Lilienthal · JCON-ONLINE 2021
• 46mArchitectural Patterns and Approaches Supporting Refactoring(...)Szymon Szylhabel · 4Developers 2019 Warszawa
• 49mFrom Macro To MicroSam Newman · GOTO Aarhus 2013
• 01h 01mMonolith Decomposition PatternsSam Newman · NDC Oslo 2019
• 57mModularizing the MonolithJimmy Bogard · NDC Oslo 2024
• 32mSplitting the monolithJimmy Bogard · LeadDev Austin 2019
• 55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable DevelopmentChris Richardson · iSAQB Software Architecture Gathering – Digital 2021