Multiple ChoiceHard 45s
Aggregate = transaction boundary
Why does DDD insist an aggregate is the consistency/transaction boundary?
Options
- 1Aggregates are clusters of related classes for readability. They carry no transactional meaning at all.
- 2Aggregates must map one-to-one onto database tables. Each root corresponds to exactly one row.
- 3Aggregates forbid eventual consistency between them. So every cross-aggregate update must be transactional.
- 4Invariants are enforced within an aggregate, so a single transaction should not span multiple aggregates
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.