Using cats to purfect your software architecture
summary
A tablet-game backend exposes a feed endpoint that initially calls a dog-food repository and directly manipulates a stomach row, causing tight coupling and failed code review; after adding a use cases layer the system loads a Cat aggregate (private stomach), runs internal digestion, and surfaces a CatDigestionException handled by the MVC API, keeping web and SQL Server as implementation details. The concrete build (Web API + DI + repositories + tests) fails at first, then passes after refactoring to the aggregate root pattern.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:28Why cats
- 0:59Virtual pets
- 1:25Demo
- 3:00What went wrong
- 4:19The sweet spot
- 4:53Cat to coffee
- 7:47Cat internals
- 9:08Cat in domain
- 10:24Cat in MVC
- 11:30Point of highest abstraction
related talks
31mArchitecting your codebase
37mAvoid the mess! Clean up your data repository
01h 29mArchitecture Beyond Clean & Hexagonal
35mFrontend Architecture: How to Build a Zoo?
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
50mShrek, Onions and Architecture
26mClear Architecture in the small
20mComposability: The New Architect in Town