Tomcat Reviews

Apache Tomcat has become almost the defacto server for serving Java-based applications on the internet. We use Tomcat for our Java web applications and just recently also for our Android software development classes.We chose Tomcat as it was the most widely-used Java web application programming server at that time. Also, most of our resources were tailored to work with Tomcat, and our colleagues who underwent Java web application development was also taught using Tomcat.Features-wise, it's a complete solution. Plus, a lot of other developers are also using it, and the project has been steadily supported by Apache.

The main gripe that I have with Tomcat is it's speed and size. Understandably, Java-based systems have the pre-conceived notion of being slow. However, being exposed to other web servers like the Apache web server really makes you wish Tomcat is as fast as it is. It does take time to load even on current hardware and newly-deployed applications also tend to load slowly during first access.Another grip is size. Size in terms of its memory usage and its installation. Again, compared to Apache, Tomcat really takes-up a lot of memory resources. As a rule of thumb, you need to have a lot of memory on the server which will run Tomcat. Installation size is also big, and it can take a while to download the installation package.

Overall, Tomcat is still a recommended product for use with Java web application development and Android application development. Though it has speed and size issues, it's still the most widely-used development web server for Java and Android web and application development. Just make sure you have a server that has more than enough memory if you use Tomcat, as it tends to use a lot of it.

We use this solution as a web application server.

It provides website hosting services.

The most valuable features of this solution are the general web server features.

It's simple and easy to use.

In terms of features, this solution is limited. It does do its job, but the enterprise-level features are missing.

In the next release, I would like to see better maintenance and administration utilities. For example, they could be simplified.

I have been using Tomcat for three years.

We are using the latest version. It is always updating.

It's a pretty stable solution.

This solution is actively being used.

Technical support is limited. We don't get very many issues, but when we do, the service is not very straightforward.

It was a default install and it was done before I arrived.

We used a vendor for the deployment.

My advice Look at all the options of server hosting before choosing Tomcat.

I would rate Tomcat a seven out of ten.

Public Cloud

- JSP/Servlet container

- Realm database for role and user management

10 years

Out-of-Memory issues, which can be solved by increasing the heap space.

Tomcat is a simple JSP/JSF container, but if you want to host J2EE applications you must switch to other solutions, such as JBOSS or Oracle Web Logic.

In-house

Tomcat is free and opensource.

We are using this solution because of the Oracle REST data services we are using.

The most valuable feature is the free EE server.

In the solution, we are using the terminal to enter command line codes for operations and management, this is difficult for me. It would be better if we had some administrator UI tools for this.

I have been using the solution within the last 12 months.

The solution is reliable.

We have approximately five people using the solution in my organization.

The initial setup is easy. However, we did have some difficulties at first that we managed to resolve. There is plenty of documentation online to help with the solution.

We did the implementation of the solution.

The solution is free.

I would recommend this solution to others.

I rate Tomcat an eight out of ten.

On-premises

The primary use case of this solution is for application services and web services.

The most valuable feature of this solution is that it supports Java Enterprise. I don't have to worry about compliance. Once Java EE runs then it's good.

The high availability is not as robust as the competition is, such as WebLogic and Jboss.

At the moment, it is dependent on how Java is working. So if Java goes this way, then Apache Tomcat follows. Apache is very tightly coupled to Java. 

The question would more be where does Java need to be? Then Apache Tomcat will follow because it's Open-Source.

I have been using Apache Tomcat for three years.

I am using the latest version.

This solution is stable. It has a lot of support because it is a part of the Apache Foundation, open source. 

I am a strong proponent of open source.

Scalability on its own is getting there. With the Cloud, you can deploy and make it scalable, but on its own, not as much. Unless, along with the cloud, you put it in a Kubernetes cluster, then it's scalable.

The first two projects from Apache were HTTP Daemon, Web Server, and then Tomcat. So it should have one of the richest support articles. Unless you're talking about and speaking with somebody personally, but the documentation for Tomcat is very good.

The initial setup was straightforward.

This is an open-source product and it's free to use.

Apache Tomcat is the application server, but the enterprise server that runs in it is Apache ServiceMix.

For anyone who is interested in using this solution, I would suggest knowing your use case, and knowing it very well.

If you can make it containerized, it's better, so that it can scale better. But, again, know your use case.

Because I have not used other hardware, there is nothing to compare with and it is hard to rate. In terms of my usage, I am happy with it.

I would rate Apache Tomcat a seven out of ten.

On-premises

Easy setup Easy configuration Reliability Stability Scalability Performance Well documented Great time to value and pricing.

Deployment automation needs some custom tooling.

I started using tomcat since version 4.X as development server with Eclipse. Then I used it as a Production server for medium to large Enterprise intranets. And finally I have setup deployments with Clustering for large ECommerce web sites with Apache HTTP Server as Front End. From these experiences I can say that Tomcat is a really performing and PRODUCTION ready server. Well tuned it can take very high loads provided underlying deployed applications are well coded as with any other JSP/Servlet Server.

• Tomcat is a popular and easy-to-use open source web container.
• It is easy for a developer to enter Java EE programming.

It helps the developers to build up their prototype system to evaluate their application design and feature testing.

• Easy to deploy.
• Developers can pack their application-needed library in a web application archive to deploy to Tomcat.

The enterprise support: Tomcat is an open source project, but for IT concerns, the enterprise support is needed when we encounter problems on it.

Tomcat Application Serve is an open source Application Server. Compared to other application servers like Jetty, Weblogic etc. this is very light weight Tomcat can be very easily configured to suit your needs. A large number of ever growing web community is there to help you out, in case you face any issue. Tomcat has been known to be very stable and has been deployed and used by many well known organizations. Also, it does not require too much of memory(RAM) to start with. It can start running in a very low memory and uses memory on as needed basis.

There are certain well known compatibility issues with some implementations of JDK Tomcat doesn't give you a performance like Apache when you have static HTML contents. And it is more suitable for hosting servlets and works best as a servlet container. Scalability is a major problem with Tomcat. When your application grows out of proportion and you have applications that draws heavy traffic, then Tomcat is not the right option and you might have to look for other options.

Tomcat is one of the best application servers and servlet container. It is very light weight and application startup consumes very low memory and it uses memory on as needed basis. Can be run on various platforms like Windows, Linux etc. Not suitable for hosting static HTML content and Scalability is a major problem with Tomcat.