Should I Eliminate Azure App Gateway for My Container Apps?

I think you should definitely ditch the App Gateway if budgeting is a concern. Directly pointing to Container Apps can handle basic load balancing, TLS, and routing, which is all you essentially need for a straightforward setup, similar to GCP's Cloud Run. If you require global load balancing, Front Door may be the solution you need.

If you don't require a Web Application Firewall (WAF), advanced routing, or private networking, going directly to Azure Container Apps might be a good move. It can simplify your setup and reduce expenses. The App Gateway is more suited for enterprises needing extensive control, but it might be excessive for simpler or smaller projects. Also, consider if this is for a non-production environment; sometimes trimming down on always-on infrastructure can yield great savings without major redesigns.

The costs for Azure App Gateway can indeed add up. The benefits include enhanced security features and improved traffic management, but on the downside, it can be quite complex and expensive. If you point your domain directly to the Azure Container App, you could save money but might lose some control. It ultimately depends on your specific needs.

In our case, we're using Nginx as a reverse proxy within a container. We don’t expose other app containers directly to the internet and utilize VNET integration and private endpoints for security.

Consider using Azure Front Door instead! It might be a better fit for your needs.