Tomcat Reviews

I use Tomcat for CM solutions, for access management.

We chose to use Tomcat because it's perfect compared to other containers that we have tested.

It's open-source and there is a lot of documentation available on the web. It has a good knowledge base.

The interface is not user-friendly.

You need to have knowledge of the operating system, and Linux to configure the solution. It is not user-friendly.

I would like to see a user-friendly interface.

I have been using Tomcat for 10 years.

I started with Version 8 and now we are using Version 9.

The stability is amazing. If it is configured properly, you won't have any issues.

It's scalable. It is possible to create a cluster with Tomcat. You can run it using Docker, in the Kubernetes platform. It is also possible to be embedded in some devices.

It's pretty much a full-stack solution with many ways to use it.

We have 30 technicians who are using this solution in our organization.

I have never used support from Tomcat. We have only used the documentation that is available.

There is a lot of documentation available on the internet, which is very helpful.

We have found a solution for questions that we have had through forums and the knowledge base.

The initial setup is neither hard nor too easy. There is a lot of documentation to review.

The time it takes to deploy really depends on your experience. If you are a beginner, it can take eight hours, and for the heavy user, it's about two hours to deploy it.

We are using the open-source version.

Read the documentation that is available on Apache.org. If you have any issues, look to see what is available on the forums and on the web.

Some people have been able to find a solution using the web.

We have not had big issues when using Tomcat. I would rate Tomcat an eight out of ten.

We are using Tomcat for one Java-based application that's used for any carrier site. We have one portal for carriers. Any external user can apply for whatever openings are there. Through that site they can apply and our HR can review their profile and invite them for an interview. Tomcat is handling all these processes.

The company decided earlier, when our database was on Oracle, that Tomcat is more suitable for Java-based applications and it's a free tool with free servers that we can download and use there.

Tomcat is user-friendly and easy to set up, especially compared to WebLogic or JBoss where some specialty is required. If you are going for Tomcat, you can use their guidelines and can set it up easily

Tomcat is used mainly for database connections. As of now, we configure that environment for any database configuration. But if any utility can integrate where we can pass the database connection as a string of details, then it should encrypt them and keep them inside. From that security perspective, Tomcat requires improvement. They should integrate this security feature.

I have been using Tomcat in my company for the last two years. In my previous company I used Tomcat for application, deployment and configuration.

Tomcat is very stable, nothing new in this one, it's a very old product. We were using this product for our small application testing back when we were in college.

In terms of Tomcat's scalability level, wherever scalability or a higher ability is required, we use a load balancer and other things to just upscale the data.

We have one 15-person team that is using it. It is exported to the internet, so external users are using it whenever they connect to the application.

We provide technical support because we have the knowledge about this product so we don't feel any external support is required as of now for Apache and Tomcat related issues.

The initial setup is very easy and straightforward.

It takes me a couple of hours for Tomcat implementation.

Tomcat is an open-source solution so we don't have licensing costs.

My advice to someone considering Tomcat is that they don't have too much load on their website. It's not for all websites. For normal sites, they can use Tomcat.

On a scale of one to ten, I would give Tomcat an eight.

The solution works very seamlessly. It is one of the best app servers at present. It has been a crucial part of our development.

All of the solution's functionalities are very useful for us.

The solution's interface and backup features could be better.

We have been using the solution for more than 12 years.

I rate the solution's stability as an eight.

I rate the solution's scalability as a seven. We plan to increase its usage further. Although, it is challenging to scale up for more concurrent users.

We had used WebSphere earlier. Later, we switched to Tomcat as it is robust and easy to use.

I rate the solution's initial setup process as a nine. It takes approximately an hour to complete but varies depending on the application size.

We implemented the solution with the help of our in-house team.

I rate the solution's pricing as an eight. There are no additional costs apart from the standard license.

The solution is easy to manage and has good stability. I rate it as a nine.

Tomcat is a really light-weight Web Server.

Web applications with Spring can be utilized quite effectively with the help of Tomcat.

It is very easy to use for development as well as in a production environment.

It can be integrated with Eclipse as well, for rapid development.

Documentation is very good and is helpful in case of any issue.

Web apps are very easy to deploy.

I would personally like it if the admin console would show more information specifically about memory being used.

I have been using Tomcat for more than 12 years.

Tomcat is widely accepted in tech communities because getting support is really easy.

It's a rock solid Java host.

It is at the core of our production application server environment.

None that I can think of.

I've been using it for 10 years,

No, it's rock solid.

The server needs to be bounced every three months. We reboot on schedule whether we need to or not.

No issues encountered.

It's open source and the community is very helpful.

It's open source and the community is very helpful.

We used IBM WebSphere, but the cost drove us to Tomcat.

It's drop dead easy.

We did it all in-house.

No investment, and a huge return.

We bounce the servers every three months, but other than that the costs are trivial.

We looked at other products from IBM, Sun, BEA and a couple others.

Do it. Drop it in and if you have huge traffic requirements, drop it on a couple of machines and run a network balancer.

• Simplicity
• Speed of deployment

• It allows rapid application deployment for Java web container applications.
• It provides a stable platform for the application to work with.

• The documentation can be better.
• It also lacks the flexibility to configure files.
• Clustering is complicated.

I managed it for approximately three years.

No issues encountered.

No issues encountered.

It's difficult to scale/cluster.

It was straightforward.

• Lightweight
• Configurable
• High-performance
• Cross-platform
• Open source 
• It has sufficient documentation for application development

The cluster management and load balancing is a bit complex. Also, they need to improve the documentation to handle JNDI resources.

I've used it for 10 years.

Deployment is simple, however, a limitation is hot deployment.

No issues encountered.

No costs.

If you were to have no JEE applications, then it is advisable, otherwise the application server falls short.

It has a small footprint.

With this, we were able to deliver our products faster to our customers through packaging.

The configuration needs work.

I've used it for six months.

No issues encountered.

This depends on the load of the server. We had no issues, but we never ran more than application/site at a time.

No issues encountered.

I've not used customer service.

I've not used technical support.

We switched because of the nature of the application and technology.

I always design my systems simple and keep them simple as possible.

We implemented it with in-house team. We like to keep the knowledge in-house.

It was crucial and it definitely paid off.

Keep the systems simple. Try to work with open-source solutions and pay for technical support and subscription to support the projects.

Yes I always and regularly evaluate. In case of Java we evaluated all Applications servers who support JEE full profile.

I was using Apache Tomcat, JBoss AS (RedHat), WebMethods (Software AG) and IIS (Microsoft). All of them have their specialities, but depending on the goals and purpose it’s quiet easy to make a choice. Products based on Microsoft .NET do not give companies lot of options; either with Server Operating System shipped IIS, or the developer version called IIS Express. Applications written in Java, n opposite, can be accommodated on several fully-profiled or non-fully-profiled application or web servers.

Only have one application per server if possible. Do not over complicate it, and keep the variance in the configuration simple as possible.