ACL in DDD
ACL in DDD governs translation isolation, shaping system behavior under specific failure modes and workloads.
Definition
ACL in DDD is a design property concerning translation isolation. It defines how the system behaves under specific conditions — what guarantees hold, what trade-offs apply, and how the mechanism interacts with related techniques. The property is only meaningful when its preconditions are met; outside those conditions it provides no benefit and may add cost.
Context and scope
Apply ACL in DDD when designing systems where translation isolation matters. It is most useful under partial failure, high load, or correctness requirements. Pair it with observability to verify the claimed behavior in production. Do not assume the property holds without testing the specific configuration and workload.
Common misconceptions
- ACL in DDD eliminates all problems in its domain — it only bounds or shapes specific failure modes, not all pathologies.
- ACL in DDD is free once you adopt the right tool — the property depends on configuration, workload, and failure pattern, not the product label alone.
Anti-patterns
- Enabling ACL in DDD without measuring its cost in latency, availability, or operational complexity under production-like conditions.
- Assuming ACL in DDD composes safely with other guarantees — combining mechanisms can introduce new failure modes or negate benefits.
Related concepts
Authoritative source
What it is
ACL in DDD is a design property concerning translation isolation. It defines how the system behaves under specific conditions — what guarantees hold, what trade-offs apply, and how the mechanism interacts with related techniques. The property is only meaningful when its preconditions are met; outside those conditions it provides no benefit and may add cost.
When to use
Apply ACL in DDD when designing systems where translation isolation matters. It is most useful under partial failure, high load, or correctness requirements. Pair it with observability to verify the claimed behavior in production. Do not assume the property holds without testing the specific configuration and workload.
Common misconceptions
- ACL in DDD eliminates all problems in its domain — it only bounds or shapes specific failure modes, not all pathologies.
- ACL in DDD is free once you adopt the right tool — the property depends on configuration, workload, and failure pattern, not the product label alone.
Anti-patterns to avoid
- Enabling ACL in DDD without measuring its cost in latency, availability, or operational complexity under production-like conditions.
- Assuming ACL in DDD composes safely with other guarantees — combining mechanisms can introduce new failure modes or negate benefits.
Related concepts
- Anti-Corruption Layer (anti-corruption-layer)
- Bounded Context (bounded-context)