It’s most likely known by other names, but this is the one I used to describe the idea to colleagues.
We had a service that exposed a HTTP api, however the service had become brittle and hard to extend or modify. However we needed to make additions quickly, the overheads and risks of change to the original service meant comtemplating a rewrite, something we avoid.
There is another option, that is not to touch the existing system but rather apply a facade or a lightweight proxy in front of the system. Using this facade you can either direct calls to the original system, handle them directly or even pass off to a new system. HTTP systems are great for this approach, but you can apply it to others as well.
Architecture never stands still, it is never static, you need to understand that it is under constant change. Techniques that enable you to smoothly evolve your architecture safely will give you a great competitive advantage.