Mateus Guimarães :: Unveiling the Modular Monolith
summary
Argues that a modular monolith restores database transactions while giving logical boundaries, shows concrete Laravel changes: add a modules namespace in composer, move code into vertical slices, introduce PurchaseItems action and order_placed event as DTOs on an event bus. Demonstrates reduced coupling and teams working independently, and measures trade-offs: eventual consistency, harder end-to-end reasoning, added messaging layer. Recommends service providers for module loading and cites a popular modules package and an “internachi modular” alternative.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:57What is a monolith
- 8:14Code Organization
- 11:29Boundaries
- 13:15Cross boundary communication
- 20:01Event driven communication
- 24:37Data ownership
- 27:16Student access
- 27:45Benefits of modularization
- 29:31Suggestions
- 30:22Module namespace
- 31:16Packages
- 31:54Resources
- 32:35Questions
related talks
37mLife Beyond Microservices: Modular Monoliths in Laravel
47m"Modulitiche" Applications
01h 02mDistribu-ready with the Modular Monolith
57mModularizing the Monolith
28mManaging a team building a modular monolith in Laravel
57mDistribu-ready with the Modular Monolith
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
40mEngineering Complex Applications with Laravel 4