Igniting Clean Architecture
summary
Clean Architecture centers on a layered system where business logic lives in use cases and dependencies point inward following the Golden Rule, isolating Flask/Python front ends from repositories implemented with SQLAlchemy talking to Postgres. Examples show translating HTTP to simple structures, injecting repository interfaces for testable unit and integration tests (Docker for databases), migrating incrementally from messy legacy code, and a free Python book that reproduces the runnable item-list example. Unix longevity (≈50 years) motivates durable design.
AI-written summary · about
chapters (17)
- 0:00Welcome to Clean Architecture
- 1:06Architecture history and purpose
- 4:42Why architecture matters
- 7:11Tools vs problem-solving
- 7:55Clean maintainable code
- 9:20Clean Architecture principles
- 11:08Layered system example
- 13:40Business logic separation
- 15:51Dependency injection in practice
- 17:15Data translation between layers
- 20:28Testable isolated components
- 23:18Flexible architecture benefits
- 25:22Migrating legacy systems
- 27:51No single architecture fits all
- 30:44Further reading
- 31:47Growing via architecture
- 32:56Q&A
related talks
40mOh Python! Where Did We Go Wrong
21mPythonic DDD And How To Improve Your Life When Maintaining A Monolith
46mOn Being Pythonic
24mPython for Humans, Designing Python Code Like a User Interface
41mEcosystem for Reliable Python Programming
26mDesigning APIs with Flask
01h 10mKeynote 2: Robust Python and Why It Matters
50mBest Practices for Python in the Cloud