The goal of this guide is to provide help on how to split up a Rails monolith towards a modular monolith. Or, if you’re about to get started help you to think the modular monolith way.
Some books that will help you get on your way.
- Domain Driven Design
- Component-Based Rails Applications
- Modulair Rails (Not affilated with this site)
- Domain Driven Rails From Arkency
It’s easier to see where the bounded contexts are drawn.
You only need to test the engines affected and the ones up your dependency chain.
If you have your boundaries correctly defined it will be easier to swap out components.
Because a change is more isolated to a specific domain the changes will be confined to that module only.