Exercise

Domain-Driven Design: Check Your Understanding

Six questions covering strategic design, aggregates, value objects, CQRS, event sourcing, and the repository pattern from this learning path.

1. What is a 'Bounded Context' in Domain-Driven Design?

A microservice's Docker containerA shared kernel used identically by every subdomainA physical database boundary enforced by a DBAAn explicit boundary within which a particular domain model applies with a consistent, unambiguous meaning

2. What is the primary responsibility of an Aggregate Root?

To expose every internal entity's setters directly, for flexibilityTo act as the single entry point that enforces invariants across the aggregate's internal entitiesTo store the aggregate's data spread across multiple databases for scalabilityTo eliminate the need for a repository

3. Which characteristic distinguishes a Value Object from an Entity in DDD?

A Value Object has a unique identity that is tracked over its lifetimeA Value Object must always be persisted in its own dedicated tableA Value Object is defined entirely by its attributes, is immutable, and is interchangeable with another instance holding equal attributesA Value Object can only ever wrap a single primitive type

4. What does CQRS (Command Query Responsibility Segregation) separate?

Synchronous APIs from asynchronous APIsThe model used for writes (commands) from the model used for reads (queries)Unit tests from integration testsFrontend code from backend code

5. In Event Sourcing, how is an entity's current state determined?

It's derived by replaying the full sequence of stored events for that entityIt's read directly from a single row that gets overwritten in placeIt's cached once and never recalculated againIt's taken from the most recent snapshot only, with all prior events discarded

6. What is the main purpose of the Repository pattern?

To replace the need for an ORM entirelyTo handle HTTP routing for domain entitiesTo mediate between the domain model and the data mapping layer, exposing a collection-like interface for retrieving and persisting aggregatesTo expose raw SQL queries directly to the domain layer

Sulu CMS · Next.js

Domain-Driven Design: Check Your Understanding | Architecture Hub