Apache Tomcat vs. NGINX

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Tomcat
Score 8.8 out of 10
N/A
Tomcat is an open-source web server supported by Apache.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…N/A
Pricing
Apache TomcatNGINX
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache TomcatNGINX
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Apache TomcatNGINX
Considered Both Products
Apache Tomcat
Chose Apache Tomcat
Apache Tomcat is very smooth tool compared to other applications. Since there are very less feature it's very smooth. NGINX server doesn't need Apache Tomcat we can directly deploy so it faster comparatively. In my working time I have never come across the UI of NGINX. Apache …
Chose Apache Tomcat
Apache Tomcat is lightweight but performs well, even when running multiple applications. Its performance and security features are the reasons for choosing Apache Tomcat among its competitors. Also, there is a huge community support than other products.
NGINX
Chose NGINX
Nginx's cache mechanism is better than Apache and HAProxy. Also Nginx is very light weight and works for multiple sites with much less work. i.e. As front end proxy server configuration is very easy as compared to other applications. Apache sometimes crashes and is not able to …
Chose NGINX
The support and ability to provide near zero downtime for changes is a winner. The lightweight engine also helps reduce cost.
Chose NGINX
How does it compare? We use Apache ATP server and we also use Tom Cat also owned by Apache, but both Apache, ATP, and MKA. They are relatively older than GX and so they're one problem for Apache and MKA they need more power, more memory, and more space.
Chose NGINX
NGINX have higher market share which obviously show to us it is the preferred choice of most of the customers. Both of platform competes in the Web and Application server areas, but due the security features of NGINX be more flexible this in my opinion makes more sense.
Chose NGINX
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.
Chose NGINX
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 …
Top Pros
Top Cons
Features
Apache TomcatNGINX
Application Servers
Comparison of Application Servers features of Product A and Product B
Apache Tomcat
9.0
24 Ratings
12% above category average
NGINX
8.2
21 Ratings
3% above category average
IDE support9.122 Ratings7.310 Ratings
Security management8.724 Ratings8.018 Ratings
Administration and management8.424 Ratings8.018 Ratings
Application server performance8.224 Ratings8.618 Ratings
Installation9.924 Ratings9.418 Ratings
Open-source standards compliance9.424 Ratings8.016 Ratings
Best Alternatives
Apache TomcatNGINX
Small Businesses
NGINX
NGINX
Score 9.0 out of 10
Apache HTTP Server
Apache HTTP Server
Score 8.2 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.0 out of 10
Apache Tomcat
Apache Tomcat
Score 8.8 out of 10
Enterprises
NGINX
NGINX
Score 9.0 out of 10
Apache Tomcat
Apache Tomcat
Score 8.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache TomcatNGINX
Likelihood to Recommend
8.9
(24 ratings)
8.9
(48 ratings)
Likelihood to Renew
10.0
(1 ratings)
9.1
(1 ratings)
Usability
8.0
(3 ratings)
9.0
(1 ratings)
Availability
6.0
(1 ratings)
-
(0 ratings)
Performance
9.0
(2 ratings)
-
(0 ratings)
Support Rating
9.1
(3 ratings)
8.1
(4 ratings)
Configurability
8.0
(1 ratings)
-
(0 ratings)
Ease of integration
9.0
(1 ratings)
-
(0 ratings)
Product Scalability
9.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache TomcatNGINX
Likelihood to Recommend
Apache
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.
Read full review
F5
[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.
Read full review
Pros
Apache
  • Fast to start up, which is useful when we need to just check that our changes are working correctly.
  • Free, which allows us to not be involved with the finance/legal team about using it.
  • Bundled with Spring Boot, which makes it even more convenient for our testing.
Read full review
F5
  • 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)!
Read full review
Cons
Apache
  • 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.
Read full review
F5
  • 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.
Read full review
Likelihood to Renew
Apache
We have a huge knowledge of the product within our company and we're satisfied with the performance.
Read full review
F5
Great value for the product
Read full review
Usability
Apache
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.
Read full review
F5
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.
Read full review
Reliability and Availability
Apache
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.
Read full review
F5
No answers on this topic
Performance
Apache
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.
Read full review
F5
No answers on this topic
Support Rating
Apache
Well, in actuality, I have never needed support for Apache Tomcat since it is configured and ready-to-go with no configuration needed on my end.
Read full review
F5
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.
Read full review
Alternatives Considered
Apache
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.
Read full review
F5
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
Read full review
Scalability
Apache
It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm
Read full review
F5
No answers on this topic
Return on Investment
Apache
  • 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.
Read full review
F5
  • 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.
Read full review
ScreenShots

NGINX Screenshots

Screenshot of Overview of the NGINX Application PlatformScreenshot of NGINX Controller - MonitoringScreenshot of NGINX Controller - Configuration