Apache Web Server (Apache HTTP Server) is an open source HTTP web server for modern operating systems including UNIX and Windows.
N/A
Apache Tomcat
Score 8.0 out of 10
N/A
Tomcat is an open-source web server supported by Apache.
N/A
Microsoft IIS
Score 7.4 out of 10
N/A
Microsoft IIS is an application server and infrastructure.
N/A
Pricing
Apache HTTP Server
Apache Tomcat
Microsoft IIS
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache HTTP Server
Apache Tomcat
Microsoft IIS
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Apache HTTP Server
Apache Tomcat
Microsoft IIS
Considered Multiple Products
Apache HTTP Server
Verified User
Engineer
Chose Apache HTTP Server
Against Nginx: Mainly- it's been in the field the longest. There's not really a reason to move to Nginxon 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 …
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 …
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 …
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.
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 …
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 …
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 …
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 …
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.
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.
I've used Microsoft's IIS and IBM's HTTP server. The major and a clear advantage of Apache web server over these products is that it’s free and has no licensing issues. Being in the industry for quite sometime (oldest web server) a lot of products and customizations have been …
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 …
Apache Tomcat is a much wider open standard than Microsoft IIS. It also seems to use fewer resources and is simpler to maintain. Troubleshooting when an issue arises is difficult. We had trouble managing the Tail logs when something strange happened. Logging is very complex and …
It's clear that JBoss is a full JEE stack implementation while Tomcat isn't, but if you don't need the whole JEE stack there are many lightweight alternatives that implement the required feature with Tomcat.
IIS much easier to install, configure and maintain in a Windows environment. Tomcat is more appropriate when it comes bundled with third party applications.
Director, eCommerce Analytics and Digital Marketing
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 …
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 …
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.
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 …
Microsoft IIS is a lot more easier for Microsoft .NET developers to integrate and configure. It is MUCH more easier to install and therefore less time consuming to deliver applications to end users. IIS can be installed with a few clicks of a button by anyone with …
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 …
Microsoft IIS is more simple to configure and also to maintain against other solutions. Often IIS help me to troubleshoot with its administartive tool.
Apache is java. Java is unnecessary complex. No developer wants to invest in learning all the hundreds of text based configuration files to get something done. Also, apache gives you the most evil and un-usable user interface possible. [Microsoft] IIS makes [life] after …
Positive: Better integration with Active Directory
Negative: Appache Tomcat is open source and can be deployed on all operating systems including Linux, which allows for easier cross-platform deployments.
I have had a couple of tries at using Apache and Linux as a whole but I guess I am not of the right mindset to get over the learning barrier to make this work.
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 …
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 …
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 …
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.
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.
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 …
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 …
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.
In my experience, Microsoft IIS was definitely easier to wrap my head around and also to troubleshoot. The GUI was a great visual way to see what "sites" and "app pools" you have, what is running, what is currently up.
Microsoft IIS also offers the flexibility to have multiple …
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 …
As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative.
On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.
Excellent value for companies wishing to host Java applications in the cloud. Utilizing hosting tools such as load balancers and network and application firewalls, Tomcat can be part of a powerful system to host web applications to thousands of users. There has been consistency in the development and support of Tomcat since its initial release in the late '90s and the best commonalities have been carried forward. If you host Java web applications, Tomcat is as good as any for an application server.
Publishing applications or websites is easy with Microsoft IIS. You don't need external software or complicated tutorials involving command lines and editing configuration files. On other hand, sometimes the troubleshooter needs a high knowledge of Windows Server, Registry, and tools to debug the application. If you need to host non-Microsoft technology as PHP pages or have a low budget, I recommend IIS equivalent software as Apache.
Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special
Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.
Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.
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.
The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.
Security options and advanced configurations are not easy to set up and require an additional level of expertise.
Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.
Using tomcat manager to troubleshoot is not very informative. Error messages are vague, you have to dig into log files for more information about the problems.
Is great for simple web applications, but may not work for heavy development which may require a full J2EE stack, might like JBoss better.
Security in tomcat is not straightforward, as I discovered that you have to understand how to set up realms in tomcat in order to hash passwords, which I was not overly familiar with, which is a big deal when setting up users in the tomcat-users.xml file.
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.
Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.
As I've mentioned earlier, Microsoft IIS is very simple and easy to use. The user interface is a little bit overloaded with a huge number of different options, but once you have a little clue of what you are doing and what you need - no issues at all.
Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.
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.
Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.
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.
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.
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.
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 Apache it is.
Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it requires less memory to operate, you may realize that it is very efficient.
Apache is java. Java is unnecessary complex. No developer wants to invest in learning all the hundreds of text based configuration files to get something done. Also, apache gives you the most evil and un-usable user interface possible. [Microsoft] IIS makes [life] after development easy, which is already complex enough to be bothered by something as mundane as exposing your work over the internet.
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.
Tomcat is cheap and very quick to deploy, so it has benefited much when situation needs applications to be deployed quickly without wasting time on licensing and installations.
Plenty of documentation available so no vendor training is required. Support contract is not needed as well.