Apache HTTP Server vs. Microsoft IIS

Well Suited: Perfect for hosting your own website. And, I don't mean just an individual with a port of MySpace. I mean an industrial strength, commercial grade replacement for Microsoft IIS. If you need a web server that provides a feature-rich environment with support for multiple sites (hosted in the same server), with such features as virtual hosting, and modular feature design, than Apache Web Server is right on the money. Less Well-Suited: Single page, small feature-set websites. Apache is a lot of trouble for developers to set up, just to send/receive JSON strings of a few bytes. You're really better off using something smaller and faster/simpler (lighttpd for example).

Incentivized

IIS as a web application server is perfectly suited for .net, .net core, asp.net applications. Our core ESB runs on IIS and has hundreds of gigabytes of data moved through it every day spread across millions of transactions. We have other mission critical applications that deliver our results to patients and doctors relying on IIS web application servers. If you stay in the Microsoft development stack, IIS is a top tier, efficient, and reliable web server.

Incentivized

• Apache is Open Source, governed well (the foundation) and probably the most stable computing platform ever.
• Apache is probably one of the most customizable and configurable pieces of software that I have ever run across in more than 30 years of development.
• If there is something that Apache can not do, then you need to ask yourself; should I be doing that? The point here is that it is a solid solution and seems to only integrate other technologies that are of the highest caliber.
• Apache will live forever and you can not go wrong with it.

Incentivized

• A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
• IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
• IIS has proven that it is easy to configure and maintain with minimal effort.

Incentivized

• Configuration files are located on different places depending on your Linux distro.
• If you have an error on one configuration file, apache refuses to start and sometimes is difficult to know why.
• Security is not great by default, but making a todo list help when you configure a new server.

Incentivized

• For some web applications, it takes additional time to configure IIS to make a website work.
• IIS logging - it is not the strongest side of the product.
• Compared to Apache or Nginx, IIS uses way more system resources.
• Even with regular patches, IIS has many vulnerabilities.

Incentivized

We have no intention to replace all applications running on top of the IIS platform. Not all applications support other platforms and not all support staff are skilled in Linux/Apache platform support. Whereas IIS may not be the best performing or most secure web platform available, for the aforementioned reasons, it is impossible not to continue use of this product.

Incentivized

In general, Microsoft IIS is an alright product. It comes natively with Windows Server. It has good enough GUI to set things up & tweak things around. Once properly setup, it runs stably enough. And with enough Powershell magic, having a CI/CD pipeline to automatically deploy a new version of the application is doable.

Incentivized

ARR (application request routing) in Microsoft IIS Server enables the web-admins to increase the web app reliability and availability through the rule based routing and load balancing of HTTP requests which in turn provides highly available server. IIS 7.0 Manager also provides kernel as well as user mode caching for faster performance and in case if the server fails, the IIS server has good amount of details logged in its log files which help understand and debug the cause quickly. Load balancing facilitates IIS server to fight against availability issues.

Incentivized

In my experience, I have never had significant issues with IIS performance. Sometimes I've experienced issues with loading time, but it is mostly related to the web site code. However Amazon, Microsoft and Google providing free cloud services with very limited resources, and in that scenario, "heavy" websites on IIS could be the issue. In other situations - performance is good.

Incentivized

I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.

Incentivized

As mentioned earlier there is so much documentation or guides or stack overflow questions out there that someone will have faced the same or very similar scenario to what you are going through that you will almost certainly find a solution to what you are after.

Incentivized

The comparison with other products from IBM or Oracle is difficult. These are mostly software that has to be paid for. The only fair comparison at eye level is probably the NGINX web server: It is also free and offers even higher performance. In the meantime, there is also a paid Plus version of NGINX. This has extended support and special functions.

Incentivized

On Windows, Microsoft IIS is easier to implement and maintain than Apache web service. Normally if you need to host PHP or other apache native content on a Windows server, it's recommended to use WAMP or equivalent software to simplify the installation, administration, and configuration of resources. However, you can use Microsoft IIS and other web services on the same server, taking care to keep separate folders and port usage for each system.

Incentivized

Microsoft IIS Server is scalable if the underlying server configuration is done correctly. Use x64 edition v/s 32bit and using 32bit mode application pools are some of the tweaks to be done to make the IIS server scalable. There are too many small configurations need to be carried out in order to make a highly scalable IIS server hence not giving full score in this area.

Incentivized

• Apache web server helped us in building client applications without much investment in the underlying server configuration which gives us the ability to start on a new project quickly and upgrade its resources as and when needed.
• Using software which is well-supported by a community of open source contributors makes tasks easy and affordable when need help since a couple of minutes on Google saves a couple of dollars every time and you don't need a specialized support person unless there is something significant needing to be changed.

Incentivized

• Speed of development. You don't need to be an expert to expose your website through some DNS
• Robust, there has never been any downtime because of IIS itself.
• The ease of use can have (and has had) some negative impact because it's too easy to implement something, and then forget. When a server is taken down, those unthoughtful implementations come to light the hard way.

Incentivized