The author introduces the concept of an ambassador service, which acts as an out-of-process proxy that helps with network requests on behalf of a client service or application. This pattern is useful for tasks such as monitoring, logging, routing, and security, particularly for legacy applications that are difficult to modify. The author suggests putting client frameworks and libraries into an external process that acts as a proxy, allowing control over various features and avoiding access restrictions. The ambassador can be managed independently and can be updated without affecting the application’s functionality. The author provides considerations and when to use or not use this pattern.
https://learn.microsoft.com/en-us/azure/architecture/patterns/ambassador