TrustRadius: an HG Insights company

Apache HTTP Server vs. Microsoft IIS

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache HTTP Server

    Score8.4 out of 10
    N/AApache Web Server (Apache HTTP Server) is an open source HTTP web server for modern operating systems including UNIX and Windows.N/A

    Microsoft IIS

    Score8.5 out of 10
    N/AMicrosoft IIS is an application server and infrastructure.N/A
    Pricing
    Apache HTTP ServerMicrosoft IIS
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Apache HTTP ServerMicrosoft IIS
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Community Pulse
    Apache HTTP ServerMicrosoft IIS
    Considered Both Products
    Apache
    Chose Apache HTTP Server
    Against Nginx: Mainly- it's been in the field the longest. There's not really a reason to move to Nginx on it's own. Apache has a mountain of documentation and how-tos that extend from the Foundation itself, to Individual Developers, spanning over 20 years, and most of it …
    Incentivized
    Chose Apache HTTP Server
    I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise …
    Incentivized
    Chose Apache HTTP Server
    IIS has a clear advantage over Apache: Configuration can be done through a convenient visual editor. But, sometimes, IIS can be tricky to use for serving other things than asp.net. We had bad experiences working at scale with IIS7.5 while serving PHP websites. I know that more …
    Incentivized
    Chose Apache HTTP Server
    By having a similar purpose, which is to publish and manage access to services, sites, and/or web systems, I have had to implement them to analyze their qualities and virtues, but stability, the power of implementation of different solutions and to be able to expand through own …
    Incentivized
    Chose Apache HTTP Server
    Apache lacks the scalability and feature set of NGINX but our team was not only far more experienced with Apache HTTP Server but was relying on tools and frameworks that required Apache HTTP Server. We've recently considered moving to NGINX but the workload to migrate and train …
    Incentivized
    Chose Apache HTTP Server
    To be quite honest I often select Apache because it is the world's most commonly used web server and I have been using it for more than 20 years across many organizations. I have never been burned using Apache. Apache rises above IIS in functionality, configurability, and the …
    Incentivized
    Chose Apache HTTP Server
    Apache Web Server is the oldest among all of these above-mentioned web server solutions provide a wider range of tools and support available which is of great help when creating a web app because less investment of time and money is what contributes to the success of a project …
    Incentivized
    Chose Apache HTTP Server
    I have loved Apache and the brief experience I had with IIS wasn't as good. Nginx I have heard good things and though we use it heavily for our servers now without problems, I haven't configured it myself.
    Incentivized
    Chose Apache HTTP Server
    Apache is often used in conjunction with Nginx, with Nginx in front of Apache to serve static assets like CSS and JS. Both are easy to configure. IIS is pretty cumbersome and is not as flexible as Apache.
    Incentivized
    Chose Apache HTTP Server
    Apache is far superior to Microsoft's IIS. The only reason to consider IIS would be for compatibility with a given software package that is made exclusively for IIS.
    Incentivized
    Chose Apache HTTP Server
    Apache is terrific. Zeus is actually built on Apache and adds a mediocre at best interface to controlling it. IIS is only good on Windows. Netscape servers are probably not even around anymore, but when they were, were the absolute worst. I couldn't move my office off of them …
    Incentivized
    Microsoft
    Chose Microsoft IIS
    It's difficult to compare Apache HTTP Server, nginx, and IIS - they really serve a similar purpose on a different stack. IIS is well suited to the Microsoft stack. Apache HTTP Server works well for Java web applications. nginx is a multipurpose tool that we sometimes deploy …
    Incentivized
    Chose Microsoft IIS
    In terms of the configuration on a shared volume perspective, I think the Apache HTTP Server does a better job here. The Apache angle on this problem is more efficient from a man power perspective and ends up costing a little less in the long run over time. IIS tends to scale …
    Incentivized
    Chose 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 …
    Incentivized
    Chose Microsoft IIS
    Microsoft IIS stacked up well with Apache, but since we are a Microsoft shop primarily, we had more resources that were familiar with managing the operating system and the server itself. While there are some benefits to Apache, you can find most of them in Microsoft IIS if you …
    Incentivized
    Chose Microsoft IIS
    Microsoft IIS was selected long ago as it was included with the Windows licensing. As such no new servers or costs were needed to host a site. We now host nearly 4,000 sites on Microsoft IIS. We do still use other platforms as needed but we always start with Microsoft IIS …
    Incentivized
    Chose Microsoft IIS
    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 …
    Incentivized
    Chose Microsoft IIS
    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.
    Incentivized
    Chose Microsoft IIS
    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.
    Incentivized
    Chose Microsoft IIS
    We actually use both platforms in conjunction with each other.
    Incentivized
    Chose Microsoft IIS
    Many support teams are not comfortable supporting Linux platforms which is where Apache can really shine; also, application vendors often do not support Apache on Linux whereas they do support their products on Microsoft servers running IIS. In our case, the applications that I …
    Incentivized
    Chose Microsoft IIS
    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.
    Incentivized
    Chose Microsoft IIS
    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.
    Incentivized
    Chose Microsoft IIS
    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 …
    Incentivized
    Chose Microsoft IIS
    Tomcat & HTTP Server would be naturally choice on Linux servers. In fact, they're usually embedded so you don't even have to worry about setting up a web container.

    Obviously, setting them up on a Windows server involves more effort than "just" turning on Microsoft IIS.
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    No answers on this topic
    Delivers good value for the price
    No answers on this topic
    No answers on this topic
    Happy with the feature set
    No answers on this topic
    No answers on this topic
    Lived up to sales and marketing promises
    No answers on this topic
    No answers on this topic
    Implementation went as expected
    No answers on this topic
    No answers on this topic
    Features
    Apache HTTP ServerMicrosoft IIS
    Application Servers
    Comparison of Application Servers features of Apache HTTP Server and Microsoft IIS
    Feature
    Apache HTTP Server
    -
    Ratings
    Microsoft IIS
    7.5
    28 Ratings
    IDE support00 Ratings8.020 Ratings
    Security management00 Ratings7.028 Ratings
    Administration and management00 Ratings8.028 Ratings
    Application server performance00 Ratings8.028 Ratings
    Installation00 Ratings9.028 Ratings
    Open-source standards compliance00 Ratings5.017 Ratings
    User Ratings
    Apache HTTP ServerMicrosoft IIS
    Likelihood to Recommend
    8.0
    (20 ratings)
    9.0
    (28 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    10.0
    (1 ratings)
    Usability
    -
    (0 ratings)
    10.0
    (9 ratings)
    Availability
    -
    (0 ratings)
    8.0
    (1 ratings)
    Performance
    -
    (0 ratings)
    7.8
    (2 ratings)
    Support Rating
    9.3
    (2 ratings)
    9.4
    (6 ratings)
    Ease of integration
    -
    (0 ratings)
    8.2
    (2 ratings)
    Product Scalability
    -
    (0 ratings)
    8.0
    (1 ratings)