I use Azure Front Door primarily for two main purposes: a Content Delivery Network to cache web content and a global load balancer to distribute traffic to my backend services.
The customer has numerous applications that need to be accessed over the Internet. To protect these applications and integrate them with DNS while implementing custom routes, we, the technical team, have decided to use Azure Front Door. It offers a cost-effective solution that meets these business needs.
Our website is built through a Gatsby process and generic static files. All the static content for the site gets hosted in the CDN. We use Azure Front Door as an entry point for it.
We need to use the Front Door to support our application globally. You have some users in Europe or Asia, or when on a different Internet, you can implement a Front Door, which is a good feature. You can skip all the traffic from the master guide implemented on the web. So this component is also secure, but the problem with the Front Door is the time latency.
Senior Azure Solution Architect at Tata Consultancy Services
Real User
2021-09-22T19:17:00Z
Sep 22, 2021
If you have a web application in the back end, that's what the Front Door is for: you have to have a web application firewall. Microsoft's Web Application Firewall is designed for the Application Gateway and regional load balancing, or global balancing with Front Door.
CTO Executive at a tech services company with 11-50 employees
Real User
2021-06-03T09:57:23Z
Jun 3, 2021
We tend to use every aspect of the product. We use Azure Front Door, the Web Application Firewall on Front Door, and the Application Gateway. We implement all of these solutions for our customers. It depends on the need of our customers. The solution supports a lot of data publishing work.
Azure Front Door is employed for securing external traffic, global load balancing, integrating web application firewalls, enabling disaster recovery, and enhancing application accessibility.
Organizations leverage Azure Front Door to support data publishing, act as a CDN, and ensure low latency for global users. Clients use it to protect numerous internet-accessible applications, integrate with DNS, and implement custom routes. Favored for caching web content and securely, efficiently...
I use Azure Front Door primarily for two main purposes: a Content Delivery Network to cache web content and a global load balancer to distribute traffic to my backend services.
The customer has numerous applications that need to be accessed over the Internet. To protect these applications and integrate them with DNS while implementing custom routes, we, the technical team, have decided to use Azure Front Door. It offers a cost-effective solution that meets these business needs.
Our website is built through a Gatsby process and generic static files. All the static content for the site gets hosted in the CDN. We use Azure Front Door as an entry point for it.
We need to use the Front Door to support our application globally. You have some users in Europe or Asia, or when on a different Internet, you can implement a Front Door, which is a good feature. You can skip all the traffic from the master guide implemented on the web. So this component is also secure, but the problem with the Front Door is the time latency.
This solution is a global load balancer for web applications, offering layer 7 load-balancing capabilities. We are implementers of Azure products.
If you have a web application in the back end, that's what the Front Door is for: you have to have a web application firewall. Microsoft's Web Application Firewall is designed for the Application Gateway and regional load balancing, or global balancing with Front Door.
We tend to use every aspect of the product. We use Azure Front Door, the Web Application Firewall on Front Door, and the Application Gateway. We implement all of these solutions for our customers. It depends on the need of our customers. The solution supports a lot of data publishing work.
We use it for external security filtering to protect our external traffic that is coming into Azure.