> Because there is no newly invented architecture called "modular monolith" - monolith was always supposed to be MODULAR from the start. Unless you're in a lar

> Because there is no newly invented architecture called "modular monolith" - monolith was always supposed to be MODULAR from the start. Unless you're in a large established org, modulatity is likely a counter-goal. Most startups are looking to iterate quickly to find pre-PMF. Unless you write absolutely terrible code, my experience is you're more likely to have the product cycle off a set functionality before you truly need modularity. From there, you either (1) survive long enough to make an active decision to change how you work (2) you die and architecture doesn't matter. "Modular monolith" is a nice framing for teams who are at that transition point.