Clean Architecture: Stories of Pain and Joy From the Codebase
summary
An ERP monolith was migrated to EC2 using Infrastructure as Code with Troposphere and its MS SQL database moved to Postgres to cut license costs. A Clean Architecture proof-of-concept introduced queues, background tasks, linters, and unit tests and a Strangler Fig migration was used across four teams over 8–12 months, which reduced QA defects but slowed delivery and lost funding; a contrasting microservices example showed faster merges using template-driven services and effective TDD.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:47Old ERP problems
- 3:33Architecture issues
- 4:38Cloud migration
- 7:25Migration results
- 7:46Code quality problems
- 8:27Clean Architecture
- 9:52Strangler Fig Pattern
- 10:36New architecture challenges
- 12:03Results after two months
- 13:06Testing issues
- 14:11Development changes
- 15:36Integration testing
- 16:18Lessons learned
- 17:23Alternatives for old system
- 17:46New Hexagonal project
- 19:56Hexagonal benefits
- 21:00Why Clean Architecture
- 21:43Clean Architecture in legacy
- 22:25Clean Architecture drawbacks
- 23:30Comparison with others
- 24:57Summary
- 25:39Q&A
- 27:47TDD in projects
- 29:57Code testing
- 31:01Migration duration
- 33:14Architecture tools
- 34:40Business reaction
related talks
23mClean Architecture: A Twelve Months Journey to Clarity
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
29mIntentional Architecture in Agile Organizations
41mInside Software Architecture - Where the Bodies are Buried
53mThe Grand Unified Theory of Clean Architecture and Test Pyramid
01h 29mArchitecture Beyond Clean & Hexagonal
47mBlending Product Thinking with Architecture