>As we look to displace a legacy system a part at a time, we look to identify, extract and replace application capabilities. To do this we will be introducing c

>As we look to displace a legacy system a part at a time, we look to identify, extract and replace application capabilities. To do this we will be introducing cases where both the legacy system and its replacement need to interact - be that to handle state changes, processing of commands, queries or user interactions. Often the legacy system is difficult or costly to change (addressing this challenge may be the primary reason for the displacement programme in the first place), and so we need a mechanism that can allow new capabilities provided by the new systems to be integrated, whilst minimising impacts to the legacy system. How is this different from Anti-corruption Layer pattern https://learn.microsoft.com/en-us/azure/architecture/patterns/anti-corruption-layer https://learn.microsoft.com/en-us/azure/architecture/pattern... >Implement a façade or adapter layer between different subsystems that don't share the same semantics. This layer translates requests that one subsystem makes to the other subsystem. It feels like those are very very close or almost the same concepts. Or that can achieve the same results.