Tomcat is an open-source web server supported by Apache.
N/A
cPanel
Score 8.8 out of 10
N/A
cPanel headquartered in Houston provides website hosting providers with workload and server automation, as well as a management console for creating and launching websites, managing email and web files, and other administrative tasks.
$15.99
per month
NGINX
Score 9.2 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 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 …
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'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 …
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.
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.
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.
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 …
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.
I personally use it for any website hosting I do for me and others. There are a few others but I have stuck with the old tried and true and it always works for me and I know how to get around it so it has become a breeze for me. For those who are extremely new to websites and hosting or to those with very little technical know how cPanel could be very overwhelming and they might want to do like a managed WordPress hosting where they don't really have to see or deal with cPanel. I also probably wouldn't use it for straight email hosting. If you have thousands of cPanel accounts it may get very expensive and that could be a factor.
Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.
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.
The costs can be a limiting factor for some businesses if you are not using a web hosting company that uses it. I have been experimenting with Cloud hosting, which can be very daunting for the novice. There is an option to install it on the cloud but it is expensive.
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.
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.
Although it can be a little bit bloated with a lot of options and configurations, it's very straightforward to use and maintain. So it's a great option even if you don't have large experience in hosting configuration. The WHM tool is more suited to heavy users since it requires more expertise, so it has a steep learning curve to better understand how to use it.
This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers
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.
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.
The support comes in the form of an extensive library of how to articles and community input. For most situations this will give you plenty of information and resources to trouble shoot. Live support really then would need to default to the hosting provider who provides the cPanel for your use.
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.
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.
The direct server management tool access provided by cPanel hosting accounts is far superior to any shared or "standard" web site hosting packaged offered by any of the numerous web host providers I have used and or evaluated over the 20+ years of my experience working in the internet industry.
I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives
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.
By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.
