Domain Driven Modular Architecture
summary
Explains how Domain-Driven Design (DDD) combined with modular architecture produces more maintainable, reusable, clean, and loosely coupled Java systems. Covers modularity principles and concrete code examples to show how applying DDD and modular design changes programming fundamentals and yields simpler, higher-quality designs.
AI-written summary · about
chapters (21)
- 0:00Welcome
- 2:10Monolith complexity
- 6:50Microservice misconceptions
- 9:22Distributed system challenges
- 11:49Module independence
- 13:59Domain-driven design basics
- 17:08Workflow importance
- 18:33Changing versus stable code
- 20:17Hexagonal architecture benefits
- 21:20SOLID principles role
- 22:47DDD and easy architecture
- 23:55Unit test limits
- 26:06Context and framework relation
- 29:40Modules as organisms
- 31:51Hundred times principle
- 35:03Ports and adapters
- 39:05Test isolation without mocks
- 40:30Domain events and queues
- 41:14Module independence example
- 42:38Package structure and tests
- 44:06Thanks and future talks
related talks
42mDomain Driven Design - So Your Code Speaks Plain Language
49mHow to cook Domain Driven Design
46mDomain Driven Design The Basics
38mWhat I talk about when I talk about Domain Driven design
55mDomain-Driven Design: back to the roots
48mDomain-Driven Design tactically and practically
59mDomain-Driven Design - Where Rubber Meets the Road
01h 04mDomain Driven Design: The Good Parts