The following considerations should be taken into account while implementing this pattern:

• Another layer of abstraction: Adding layers to a system architecture results in some side effects such as increase in communication latency. The maintainability and testability of the code will also be impacted with introduction of additional classes.
• Exception handling: As the consuming application interacts with the proxy instead of the service directly, it must cater for scenarios where the backend Microservice is unavailable. The proxy will need to capture any service exceptions and relay it to the client.
• Logging: All exceptions and traces should be logged by the proxy to ensure better troubleshooting capabilities.
• Abstraction: Implementation or deployment details of the Microservice should be abstracted from the client.
• Configurable: The deployment location of the Microservice should be configurable and should have the ability to be updated without code re-compilation.