where to use Envoy proxy as api-gateway or AG services as api-gateway on microservices

Question

Hi All,

Microsoft recommended use Envoy-proxy as api-gateway(URL-rewriting) as below repo.(microservices patterns)
https://github.com/dotnet-architecture/eShopOnContainers

Also , we can use Azure front-door or application gateway( APP-GW) kind service for a Public facing End point for client access and then linked to VM -scale set or AKS infrastructure as backend pool.

Is there any guidance to take decision where we can use Envoy-proxy as api-gateway or use Azure FD or APP-GW services with backed pool.

Many Thanks,

Answer 1

@Anirban Goswami , I am not much aware of Envoy but on doing research found that it works like Azure API management service. But Application Gateway and Azure Front Door are used as loadbalancing solutions Azure. You can deploy APPGW with API management to selectively expose some API’s externally whilst keeping all other API’s internal. So, to secure your internet facing API’s and to load balance the traffic across those subset API’s you need to deploy APPGW with WAF before the APIM.

----------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.