The anti-corruption layer may add latency to calls made between the two systems.

The anti-corruption layer adds an additional service that must be managed and maintained.

Consider how your anti-corruption layer will scale.

Consider whether you need more than one anti-corruption layer. You may want to decompose functionality into multiple services using different technologies or languages, or there may be other reasons to partition the anti-corruption layer.

Consider how the anti-corruption layer will be managed in relation with your other applications or services. How will it be integrated into your monitoring, release, and configuration processes?

Make sure transaction and data consistency are maintained and can be monitored.

Consider whether the anti-corruption layer needs to handle all communication between different subsystems, or just a subset of features.

If the anti-corruption layer is part of an application migration strategy, consider whether it will be permanent, or will be retired after all legacy functionality has been migrated.

This pattern is illustrated with distinct subsystems above, but can apply to other service architectures as well, such as when integrating legacy code together in a monolithic architecture.