Architecture in the Frontend
Nobody needs architecture.
Until nothing works.
Frontend architecture is not self-indulgence and not an aesthetic exercise. It's fire protection for systems that still need to change tomorrow.
The Architecture Myth
“Architecture is overrated.”
“It doesn't have to be perfect — it just has to ship.”
“Nobody needs architects.”
Maybe.
As long as everything stays small, clear, and stable.
Most systems unfortunately don't.
Architecture is usually only taken seriously once its absence becomes expensive.
Before that, it sounds like a luxury: too slow, too theoretical, too polished — too much concept for too little feature.
But bad architecture doesn't die spectacularly. It makes every change a little harder, every test a little more fragile, every requirement a little more dangerous — until eventually nobody knows anymore where it's still safe to touch things.
Where do you want to begin?
The Blunt Axe
Tools don't improve by using them less often. On the cost of doing things halfway.
Read →Sentences that get expensive
Words that surface in projects — and that you keep hearing afterwards.
Read →Decisions
DDD, micro-frontends, CRUD instead of domain — when each fits and why that's never purely technical.
Read →Field Reports
What actually works? From real projects, with real friction. No success stories without context.
Read →You're in the right place if …
- → you can't hear "clean it up later" one more time
- → your architecture diagram looks better than your repository
- → your component has more states than your project plan
- → you know that "just frontend" is rarely harmless
- → you've stopped believing the next framework will solve everything
Where do you want to go deeper?
Recommended starting points
Why this site?
What's here, why it's written this way, and who it's for.
AnalysisSentences that get expensive
A collection. Once you know them, you hear them everywhere.
Field ReportWhen does DDD pay off in the frontend?
Domain-Driven Design isn't a silver bullet. But sometimes it's exactly right.
Field ReportSCS in Reality
Self-Contained Systems sound simple. They're not.
NoteArchitecture starts small.
Before systems rot, small things get normalized: unclear states, leaky DTOs, components secretly playing use cases.
LabAgentic Flows in the Frontend
When AI doesn't just generate text, but manages state.