Azure Front Door vs. NGINX

Azure Front Door is very easy and fast to set up and implement, if you are looking for an easy solution that is secure and reliable, Front Door does all that and can be configured in a few hours. AFD is a CDN with WAF, accordingly, it is well suited for any CDN Scenario, other providers such as Akamai or Verizon have a more expensive base price and are harder to manage/configure, Front Door is simple, easy, and provides what's needed when it comes to Web App Security. If you have multiple data centers, have apps in different regions, or targeting a global audience, AFD is an excellent option to get up to speed quickly. If you are looking for more features and capabilities, or planning a very complex setup, Front Door might be sufficient, but other specialized provides such as Imperva, Cloudflare or Akamai are generally a bit more advanced (but harder to set up and maintain). It always depends on the scenario, but for us, Front Door was an excellent option and served us very well with no issues.

Incentivized

[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.

Incentivized

• Content delivery across all continents
• Web & media acceleration
• Web application firewall
• Backend geo-availability
• Reporting & access metrics

Incentivized

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Incentivized

• Better control over origin caching
• Hierarchal Management UI instead of distributed management
• TLS & Cipher Control
• Faster publishing or change updates

Incentivized

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

Great value for the product

Incentivized

Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

It's generally hard to compare CDNs, each has its features, POP locations, latency, and availability. We have used many other CDNs, including Akamai, Verizon, and Cloudflare. They are all great, but each has its own advantages/disadvantages. From our perspective, all other providers were much harder to configure and maintain and their overall cost was higher than AFD. For example, Verizon was great, performance was excellent, but reporting/logging was not up to our expectations, and we had many issues with its Rules Engine. AFD is great for delivering your web apps globally quickly and easily, the cost is reasonable and comes with very little operational overhead, the logging and reporting capabilities are very good, additionally, its integration with Azure Cloud Services gives it an advantage over other competitors.

Incentivized

We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because

• we have a large number of services and we can manage a single Nginx instance for all of them
• we have high impact services and Nginx never breaks a sweat under load
• individual services have special considerations and Nginx lets us configure each one uniquely

Incentivized

• AFD implementation was approx. 80% cheaper than other providers, from initiation to operation.
• It allowed us to minimize backend resources size/processing power, taking all the load from client requests, cutting tens of thousands of dollars monthly on compute, memory, and network bandwidth.
• Overall, the ROI of AFD is very quick, it is not an expensive solution, therefore, its ROI goals are easy to calculate and achieve, our overall ROI exceeded 300%.

Incentivized

• Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache.
• Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy").
• Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly.

Incentivized