Domain-Driven Design

Definitions

1. A software design approach that focuses on modeling the core business domain through close collaboration with domain experts. Key concepts: bounded contexts (clear boundaries between subdomains), ubiquitous language (shared vocabulary between developers and business), aggregates (consistency boundaries), and domain events. Introduced by Eric Evans in 2003.

   In plain English: Designing software by deeply understanding the business domain and organizing code around business concepts rather than technical layers.

   Example: "In our DDD model, Order and Payment are separate bounded contexts — they communicate through domain events, not shared database tables."

Related Terms

• Implementation
• Trade-off
• Hexagonal Architecture
• Twelve-Factor App
• Clean Architecture
• Abstract Class
• Abstract Factory Pattern
• Abstract Method
• System Architecture
• Testability