applying-domain-driven-design

Domain-Driven Design methodology covering strategic design (Bounded Context, Ubiquitous Language, Context Mapping), tactical patterns (Domain Model, Event Sourcing, CQRS), practical adoption (heuristics, EventStorming), and operational data decomposition with polyglot database selection. Use when designing domain boundaries, choosing business logic implementation patterns, decomposing monolithic data, or aligning software architecture with business strategy. For socio-technical architecture modernization and trade-off analysis, use modernizing-architecture instead. For microservices distributed patterns (Saga, messaging, granularity), use architecting-microservices instead. For data architecture read-side patterns and caching strategies, use architecting-data instead.