The Art of Front-end Architecture
summary
Argues for organizing front-end around business rules with a concrete five‑layer layout: domain, use cases, infrastructure, adapter layer, UI that enforces the dependency rule (dependencies point inward). Shows TypeScript examples, invokes use cases from Vue/Vuex and from jQuery, uses a tic‑tac‑toe demo and describes incremental rollout at an energy app serving more than 300,000 customers. Reports easier unit testing and framework swaps at the cost of extra indirection.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:07Legacy Code
- 5:02Business Stuff
- 10:57Dependency Rule
- 14:00Why are we complicating this
- 16:50Explicit references between layers
- 25:52Disclaimers
- 28:06Conclusion
related talks
50mThe Art of Front-end Architecture
53mClean Architecture Works in the Frontend Too!
39mClean Architecture works in the Frontend too!
22mHow to make robust and scalable front-end using layers
16mAn Architecture for Testing Your Frontend
49mSOLID Frontend Architecture. Do we need it? Yes!
39mTomorrow's UI Architecture — Structuring UI applications Around Features
18mSoftware Architecture Building Better Applications with Architecture Best Practices