Choosing the right structure for a growing app

I like monorepos when several apps share a design system and a bunch of utilities. One version of the button, one eslint config, one place to bump TypeScript. People underestimate how much drift hurts until three apps ship three different “primary” blues.

Micro-frontends are useful when teams truly need different release trains, or when one team’s bundle really can’t be allowed to take down another’s. That’s rarer than Twitter thinks it is.

My default: tighten boundaries inside one deployable first. Split later if politics or performance forces your hand, not because the diagram looked cool in a conference talk.