Chapter 7. Modular Monoliths: Driven by the Domain
There’s more than one way to build a monolith. So far, you’ve encountered the layered architecture, which aligns things technically. You can go a long way with a layered monolith, but when changes begin to involve lots of communication and coordination between different teams, you might need a little more horsepower under the hood—and perhaps even a different architectural style.
This chapter looks at the modular monolith architectural style, which divides applications up by business concerns as opposed to technical concerns. You’ll learn what this means, what to look out for, and all the trade-offs associated with this style. Let’s take the modular monolith for a spin, shall we?
As a reminder, Naan & Pop’s sandwich shop has a small development team, and its requirements haven’t changed a whole lot since the team built their layered application in Chapter 6. The competition is stiff, and time to market remains a concern. The system should remain simple.
Note
Be sure to review Chapter 6 if you need to refresh your memory.
Get Head First Software Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
