Writing / 5 parts
Part 01
Where the code lives, how many processes you deploy and how coupled the code is are separate decisions. A real project with one codebase, three deployables and boundaries checked in CI.
Part 02
Before you think about modules or services, you need to know where the boundaries are. A practical guide using Evans, Vernon and Khononov, applied to a school platform.
Part 03
A module boundary that only exists in a diagram won't survive the first tight deadline. How to make the build break when someone crosses a boundary, in Python, Java and Go.
Part 04
Enforced boundaries solve half the problem. The other half is how modules talk without coupling: when to call, when to publish an event and how not to lose events along the way.
Part 05
The real signals for leaving the modular monolith, the false ones, and a step-by-step extraction with no big bang: facade, remote adapter, events on the broker and the schema leaving last.