Microsoft IIS is an application server and infrastructure.
N/A
NGINX
Score 9.0 out of 10
Mid-Size Companies (51-1,000 employees)
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
Apache and Nginx are what we use for our large websites and public data. When dealing with the type of traffic we see on our sites IIS just doesn't scale out well. For our staff levels, Apache and Nginx are very hard to support for all of our projects so we can't always use …
Apache and Nginx are both lower overhead solutions compared to IIS, but require extensive configuration through files or command lines. For someone creating a website for the first time, these solutions are difficult to understand and implement.
Nginx is hard to support for smaller multiple projects, which is one reason we use the Microsoft IIS server, which is best fit for a set-up once and forget scenario. The Apache server is more recommended for smaller sized projects due to its cost factor, as the Microsoft IIS …
After using both Microsoft IIS and free Linux alternatives, like NGINX and Apache, I have to say I much prefer the Linux products in every way. Configuration is clearer (you have to edit config files deep in Linux somewhere, but once you've done it once, it's easy). Logging is …
IIS is easier to configure and manage. Doesn't require deep knowledge of the product to manage it. Doesn't require for IT team to learn Linux/Unix OS for basic web hosting. However, for advanced IT specialists, all three solutions could be useful and can work together.
I feel each has their own strengths, when it came to developing the in house applications ASP gave us more features so we went with IIS to support those features.
IIS is a different animal than most webservers. I don't know that I'd compare IIS to other products. The differences and reasons to use each are so diverse.
Microsoft IIS is the only official way to run ASP.NET framework sites and for Microsoft System management tools (SCCM and WSUS). While open source options like Apache and NGINX are more commonly used in our department, to maintain the best compatibility we use IIS in certain …
Nginx is one of the top three web servers and sits in the second position in terms of the amount of servers deployed. The main competition comes from Apache and Apache-based forks on Linux based servers, and less-so from Microsoft IIS on Windows based servers. As stated …
Microsoft IIS server is not open source and it comes with its own overhead in terms of cost which is not the case with Nginx as we do not need to purchase a handful of other products in order to get an HTTP server up and running. If I compare it to Apache Server, it …
Verified User
Engineer
Chose NGINX
The support and ability to provide near zero downtime for changes is a winner. The lightweight engine also helps reduce cost.
MS IIS and Apache HTTP Server both provide many similar services. However the configuration simplicity, and performance characteristics helped us choose NGINX above the other 2 products.
Nnginx is more light-weight than many other web servers, has a very expressive configuration language, easier to configure than tools like IIS and Apache, easy to install certificates for SSL, much easier to model complex routing scenarios than IIS, easier to configure than …
Other Web servers are either not performant enough or locked to a platform. The main competitor in my opinion is the Apache Web Server, that can be extended in functionality through a diverse set of modules to perform almost any task related to a network server. But at scale, I …
I selected Nginx because it is easy to learn, use, and maintain. I almost never have to troubleshoot it ever since I deploy it. It just meets my need for a personal learning experience. It works well with PHP and MySQL on Linux. That is why I chose it at first.
It's lightweight and it does not require complex configurations for simple scenarios. If you want you can accomplish some other complicated tasks like reverse proxies which are well supported by the product.