Multiple ChoiceHard 45s
Consistency boundary choice
A bank transfer must debit one account and credit another atomically. If they are in different aggregates, what is the DDD-aligned approach?
Options
- 1Span a single database transaction across both aggregates no matter what coupling cost that incurs
- 2Accept that money may occasionally vanish between the two writes and simply move on without repair
- 3Use a single global mutex held for the entire duration of the transfer flow to serialize the writes
- 4Use a saga with compensation, or model them in one aggregate if they truly must be atomic
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.