Test your Domain-Driven Design knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is "Event Storming," a collaborative workshop technique often associated with DDD practice?
In this round
What is "Event Storming," a collaborative workshop technique often associated with DDD practice?
What does it mean for an Aggregate to enforce "transactional consistency" as its boundary, and what does DDD generally recommend about referencing across Aggregate boundaries?
What is a "Repository" in DDD, and how does it relate to persistence?
What is an "Anticorruption Layer" (ACL) used for in DDD, particularly when integrating with a legacy system or external service?
What is a "Bounded Context" in DDD?
What is a "Domain Event" in DDD, and what pattern does it typically enable?
What is a common criticism or practical trade-off consideration when applying DDD's tactical patterns (Aggregates, Repositories, Domain Services) to a genuinely simple CRUD application?
What is "Ubiquitous Language" in DDD, and why is it emphasized so strongly?
What is a "Factory" in DDD's tactical patterns, and when is one typically used instead of a plain constructor?
What is the distinction DDD draws between the "Core Domain," "Supporting Subdomains," and "Generic Subdomains" of a business?
What is the general distinction between "Strategic Design" and "Tactical Design" as the two broad halves of DDD's toolkit?
What is the relationship between DDD and microservices architecture — does DDD require using microservices?