Pattern summary

What

A pattern that introduces a layer between two subsystems to prevent undesirable dependencies and preserve the integrity of the internal model.

WAFImplement a façade or adapter layer between different subsystems that don't share the same semantics.

Used with

Legacy systems, external services, or when integrating systems with differing models, protocols, or technologies.

WAFLegacy application is migrated to a modern system and it may still need existing legacy resources.

When

When you need to integrate with another system but want to avoid leaking its model or logic into your own application domain.

WAFNeed to ensure that an application's design is not limited by dependencies on outside subsystems.

Not Suitable For

Systems that already share the same domain model or when maintaining the anti-corruption layer introduces unnecessary complexity or latency.

WAFNo significant semantic differences between new and legacy systems.