Clean Architecture: A Twelve Months Journey to Clarity
summary
A year-long refactor moves a Node backend from an Express/Sequelize monolith into module-driven Clean Architecture with presenters, modular use-cases and extracted microservices, adopting Express -> TypeScript and keeping tests next to each module. Before the work, adding three product fields touches 30+ files and ~60 changes; after refactor it touches roughly five places (presenter, migration, model, maybe one controller and one use case). The approach reduces duplication, prevents cyclic deps and makes TDD and API/unit testing practical.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:08Project context and history
- 6:52Problem with legacy backend
- 9:05Clean Architecture introduction
- 10:31Three key ideas from the book
- 12:18Project restructuring with Clean Architecture
- 13:44Single Responsibility Principle in practice
- 15:10Extracting presenters for decoupling
- 17:44Results and improvements after changes
- 18:50Testing and TypeScript adoption
- 20:56Benefits of TypeScript and typing
- 22:25Summary and key takeaways
related talks
37mClean Architecture: Stories of Pain and Joy From the Codebase
53mClean Architecture and How It Helps Build Microservices and Microfrontends
53mClean Architecture Works in the Frontend Too!
39mClean Architecture works in the Frontend too!
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
35mRethinking Enterprise Architectures with Node.js
25mPrinciples for Scaling Frontend Application Development
41mOne year of Clean Architecture: the Good, the Bad and the Bob