Azure Application Gateway vs. Cloudflare

For building scalable and highly available applications, Azure Application Gateway does most of the job on behalf of you; automatically load-balancing traffic from a number of users to a number of back-end servers. This ensure scalability and availability. The in-built security is great as can be expected from Microsoft, and user has a variety of tools for monitoring the health of the load-balancing function as well as the health of back end servers behind it.

Incentivized

It is easy to set up, and within 10 minutes it is up and running. You can add many domains in one dashboard. So no need for a separate Cloudflare account. I can access all my domain DNS, and customize/add it further. For example by adding the Google Webmaster DNS key or my email provider.

Incentivized

• Easy integration with Load Balancer and Azure Scale Set to provide a full solution for traffic management.
• With rich routing rule, we could use one Application Gateway as the central point for all internal applications to expose to the external network.

Incentivized

• Registrar and DNS services are impeccable, with registrations done at cost and without ADs. DNS services setting standards for speed of resolution.
• DDOS protection. With their content distribution network to back them they have the bandwidth and tools to be both proactive and reactive to bad actors.
• WAF - Their Web Application Firewall helps mitigate common site vulnerabilities and has active zero-day protection running for breaking exploits

Incentivized

• Live examples in the Azure documentation
• Application Gateway UI Blade in Azure Portal can be streamlined
• Have more advanced feature set as WAF (Web Application Firewall)

Incentivized

• In some cases, using Cloudflare can actually lead to slower website speeds if the network is congested or if the website's traffic is particularly heavy.
• Some website owners may find that the level of customization offered by Cloudflare is limited, especially in comparison to other solutions.
• While Cloudflare is easy to set up and manage, it may be too complex for users who are not familiar with web technologies.

Incentivized

lower cost

Incentivized

Everything is extremely concise and all settings apply immediately and take effect globally. There is no reason to explicitly plan/think in terms of individual regions as one would have to traditional cloud offerings (AWS, OCI, Azure). All Cloudflare products integrate seamless as part of a single pipeline that executes from request to response.

Incentivized

In 6+ years of relying on Cloudflare, I think we experienced one or two brief outages that were Cloudflare's fault.

Incentivized

Their Argo for the global network is the core feature we love.

Incentivized

I don’t like that it's part of the Microsoft brand. In general, I am not a fan of Microsoft products but Azure gets it right.

Incentivized

We really like to talk to a person on the phone or using chat. But the system is very slow and sending to much email to get the issue solve. Something we don't like to spend time writing on the community forum our issue because we don't want to share detail information of our POC.

Incentivized

Very well executed implementation where our team was able to handle the implementation with guidance.

Incentivized

Other load balancing tools in Azure (Azure LB and Azure Traffic Manager) are limited in their functionality in comparison with the Azure Application Gateway, and also, they don't provide security features. Azure Firewall, although it has security features, is more expensive, and most importantly, it's not a load balancer at all.

Incentivized

Firebase can be a good starter for basic projects but as I scaled up, I found it lacking the maturity Cloudflare has. Naturaly, I opted for Cloudflare for bigger projects. I still use Firebase, but for small scale hobby projects only.

Incentivized

They are built for scale and have the capacity to handle all the traffic we could ever expect to get.

Incentivized

• Costs increased for the company, so expenses were more than before.
• Was able to get better user experience so users won't feel the website is useless.

Incentivized

• A lot of requests are cached and so egress costs from downstream providers are mitigated.
• DDoS protection has also managed to keep our site up and our cloud computing bill down.
• Setting up a proxy with a worker made putting various Google Cloud Functions running behind a single URL very easy and performant. Plus they offer API Shield on top of this.