Pythonic DDD And How To Improve Your Life When Maintaining A Monolith
summary
Describes how Databand.ai refactored a growing Python monolith by applying Domain-Driven Design practices—bounded contexts, layering, unit of work, repository pattern and domain architecture—to impose backend guidelines and make the codebase maintainable. Covers the problems that emerged from a quick-and-dirty startup web app and the concrete DDD-based approach they used to fix legacy issues and prevent future ones.
AI-written summary · about
related talks
45mUsing DDD To Decompose Your Monolith
39mLessons Learned from 10+ Years with Domain Driven Design
38m7 Years of DDD: Tackling Complexity
59mDomain-Driven Design - Where Rubber Meets the Road
38mWhat I talk about when I talk about Domain Driven design
44mStrategic Domain-Driven Design for dummies
56mDDD in Microservices: Complexity versus Complexity
45mDon't Overdose on Domain-Driven Design