This is part 1 of 8 of the free series Frontend system design for enterprise applications , first published on tt-tech.io .
A presentational component imports a store "just this once". Five years later, half the ui folder knows about the backend, and nobody can restyle a button without a regression in transfers. That is how enterprise frontends age: not through one bad decision, but through a boundary nobody enforced.
Architecture is the part that outlives the framework, so it comes first in this series. The question is not which pattern you pick. It is which lines your teams may not cross, and what stops them.
Layers with a "may import" contract
Split the code by type, not only by feature: domain (pure models and rules), data-access (the only code that talks to the backend), ui (inputs and outputs only), feature (wires the three), and app (shell and routes). Then write down who may import whom.
With one team this feels like ceremony.…