PodRocket - A web development podcast from LogRocket Modularizing the monolith with Jimmy Bogard
Sep 11, 2025
Join Jimmy Bogard, the mastermind behind Automapper and Mediator, as he delves into the art of transforming monolithic systems into more modular architectures. He discusses the crucial importance of defining boundaries and the perils of distributed monoliths. Learn practical refactoring techniques, database migration strategies, and insights from industry giants like Stripe and WordPress. Bogard also explores the implications of team dynamics, effective communication, and emerging AI tools in simplifying system complexities.
AI Snips
Chapters
Books
Transcript
Episode notes
Add Boundaries Before Splitting
- Start by adding explicit boundaries inside the monolith before ripping it into microservices.
- Boundaries let you learn the correct split without paying distributed-system costs early.
Avoid Tiny Distributed Services
- Avoid making everything tiny and distributed (e.g., single-purpose lambdas) because it creates distributed-system complexity.
- Stop before distributed transactions, exploding latency, and a thousand API calls per request become your problem.
Boundaries Are Formal Contracts
- A boundary means formalized ownership: interface, security, data and behavior rules for that area.
- Making interactions explicit prevents ad-hoc coupling and preserves consistent behavior across teams.
