Domain-Driven Design
DDD
ELI5 — The Vibe Check
DDD says your code should speak the same language as the business. If the marketing team calls it a 'Campaign', your code should have a Campaign class — not MarketingEmailBatchJobEntity. It forces developers and business people to actually talk to each other.
Real Talk
Domain-Driven Design (Eric Evans) centers software design around the core business domain. Key concepts include Ubiquitous Language (shared vocabulary), Bounded Contexts (explicit boundaries between subdomains), Aggregates, Entities, Value Objects, and Domain Events. Suited for complex business logic.
When You'll Hear This
"In DDD, the domain model reflects the business vocabulary." / "We need to define bounded contexts before splitting into microservices."
Related Terms
Bounded Context
A bounded context is a boundary where a particular model and language applies. 'Customer' means one thing in Sales and something different in Shipping.
Clean Architecture
Clean Architecture is like an onion with strict rules: the inner layers (your core business logic) have absolutely no idea the outer layers (databases, API...
CQRS
CQRS says: the way you write data and the way you read data should be separate systems. Writing (commands) goes to one model optimized for transactions.
DDD (DDD)
DDD is the abbreviation for Domain-Driven Design — the practice of making your code speak fluent Business.
Event-Driven Architecture
Event-Driven Architecture is like a gossip network. When something happens (order placed!), it broadcasts the news.