Deconstructing the Monolith
summary
Shopify breaks a tangled Rails monolith into a modular monolith, reassigning roughly 6,000 Ruby classes into business components, enforcing boundaries with an in‑house tool called packwork (wedge used earlier) and mounting components as Rails engines for new services like Shopify Fulfillment Network. CI rejects new dependency violations, teams own components programmatically, onboarding and on‑call routing shrink dramatically, and thousands of developers now work productively in one deploy while keeping a clear path to extract services.
AI-written summary · about
chapters (8)
- 0:00Shopify’s monolith journey
- 7:28Monolith in software design
- 13:45Outgrowing your monolith
- 20:03Code by business domains
- 27:23Reevaluating componentization
- 33:15Lessons for new products
- 38:36Benefits of modularizing
- 39:20Q&A
related talks
34m"Taming your Rails monolith"
54mTechnology constraints drive automation
30mMonolith-ifying perfectly good microservices
57mModularizing the Monolith
40mContainerizing Your Monolith
33mAdventures with Micro Services in Rails
43mBreak Up the Monolith: Testing Microservices
56mFrom Homogeneous Monolith to Heterogeneous Microservices Architecture
