Considering Migrating a Monolith to Microservices?

on YouTube ↗39m

" summary

Argues a decision method: weigh five dark energy forces (simplicity, team autonomy, fast pipeline, tech stacks, special resource/criticality) against five dark matter forces (local interactions, efficiency, ACID vs Saga pattern, runtime and design coupling) to pick which monolith parts become services. Recommends modularize and fix DevOps first, use the Strangler fig pattern for incremental extraction, and cites a real case where a machine learning service was split out to Python with faster deploys and clearer ownership.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 20:38Fast deployment pipeline
3. 21:25Optimizing a monolith's deployment pipeline
4. 23:21Support multiple technology
5. 33:49Minimize runtime coupling
6. 34:48Minimize design time coupling
7. 36:45Consequences of dark matter forces

" related talks

• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 37mEvolutionary Architecture & MicroservicesRebecca Parsons · GOTO Chicago 2015
• 38mFrom Monolith to MicroservicesDharwin Aarón Pérez Rodríguez · PyCon Latam 2019
• 32mSplitting the monolithJimmy Bogard · LeadDev Austin 2019
• 01h 03mFrom Monolith to Microservices: Story and PracticeKonstantin Gustov · DotNext 2018 Moscow
• 43mMicroMonolith - Top anti-patterns of distributed systemsMichal Franc · NDC Oslo 2016
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017
• 50mEmbracing MicroservicesGrzegorz Piwowarek · Build Stuff 2024