Anti_Corruption_Layer.md

Anti-Corruption Layer (ACL)

• Motivation
• Solution
  • Concepts
  • Implementation
• Pros & Cons
  • Pros
  • Cons
• Consideration
• When To Use
• References

Motivation

• When systems based on different models are combined, the need for the new system to adapt to the semantics of the other system can lead to a corruption of the new system’s own model.

Solution

Concepts

• Place an adapter layer between 2 domain models and translate communications between them.

Implementation

• General advices
  • The anti-corruption layer can be implemented as a component within the application or as an independent service.
  • The anti-corruption layer can be bidirectional.
  • Functionality can be added to the anti-corruption layer if it is specific to the relationship of the two subsystems, like audit log or trace logic.

Pros & Cons

Pros

• Improve the isolation and reduce the friction between the 2 domain models.

Cons

• May add latency to calls made between the 2 domain models.

Consideration

When To Use

Two or more domain models have different semantics, but still need to communicate.

References

• Book: Chris R.(2018). Chapter 13 Refactoring to microservices, Microservices Patterns (pp. 428-471). Manning Publications
• Web Article: Anti-Corruption Layer pattern | https://docs.microsoft.com/en-us/azure/architecture/patterns/anti-corruption-layer
• Book: Eric E.(2003). Chapter 14 Maintaining Model Integrity, Domain-driven design (pp. 331-396). Addison-Wesley Professional