Implement a Monolith. But Make It Modular with Well-Enforced Boundaries
summary
A case study showing how to implement a modular monolith from an existing monolithic product by modularizing code: moving classes between packages, restricting access, and defining shared models. It demonstrates enforcing module boundaries using the ArchUnit tool rather than relying on manual code review, assuming module boundaries have already been designed.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:10Why modular monolith
- 10:39Module APIs and tests
- 18:08Module challenges
- 27:04ArchUnit and rules
- 35:11Implementation and team
- 43:42Summary
related talks
50mImplement the monolith - the one well modularized
59mMajestic Modular Monoliths
01h 01mModular Monolith Instead of Microservices: How, When and Why
47mModular Monoliths
45mOnce Upon a Time... Modular Monolith: The Quest for the Perfect Architecture
43mModular Monoliths: The Architecture That Scales w Your Domain
53mCrafting a self-documenting Modular Monolith with DDD principles (theory not included)
01h 01mBetter Monoliths — Modulithic Applications with Spring Boot