# Overview A design approach that emphasizes building in a one-to-one relation with the business domain of the system. This approach blends well with the concepts of [[agile]] and a [[Microservices Architecture]], but can be used for [[monolith architectures]], too. # Key Considerations Every entity should be associated with only one context. This means you need to move away from the relational database way of thinking, where you have a singular "product" object that is used for both the warehouse and store context. ![[2025-04-04_Domain Driven Design (DDD)-1.png]] # Implementation Details # Useful Links # Related Topics ## Reference #### Working Notes #### Sources - Recommended books: - Domain-driven Design Distilled by Vaughn Vernon