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.

Tomcat allows me to deploy my Java app servers. I use it very heavily as a Java server, and it also doubles up as a web server. So my web and application server gets serviced out there. Then, I have my reverse proxy in front and put the Apache web server. So that feeds the request across to the Tomcat servers, and the Tomcat servers service it. In Tomcat, I can write the JSP code that services the pages and embed my jQuery code, which will then look up the database at the back end.

I can set it up in a completely horizontally scalable Kubernetes cluster and drive that through. My cluster manager allows me to load balance, providing massive scalability. I can deploy a thousand app servers concurrently and very easily. That is the power of Comcast.

I love Tomcat for its scalability, reliability, availability, and steadiness. There are a lot of bots that come and hit and a lot of RPA codes that come and corrupt. RPA tools themselves create a lot of bugs because they come and try to instrument and automate a lot of things. The people who have written that code are not very up to the mark in terms of not messing with the app servers.

Sometimes, the app servers get corrupted, and then they hang. So, I should be able to instrument it in such a way that my Kubernetes cluster takes over and switches it to another app server, and it blocks the RPA from coming and touching it. I can do that with Comcast very easily.

Java has not been very good for some time in the middle, and then, again, they have improved. I have to ensure that the binary codes are compiled and set up correctly. I have to ensure the classes are done and the framework is correct. When I look at the classes, I need to be able to identify the entire framework correctly.

Therefore, I need to push it to the documentation framework, which will automatically take the software code and ensure the documentation is happening correctly. Java functions should be built better into the solution.

I have been using Tomcat for 15 years.

It takes around ten minutes to deploy Tomcat.

With Tomcat, it is very easy to spin up and deploy the instances. Managing and debugging the code sets saves a lot of time and money.

Tomcat and Apache have no user interface; we do it on the command line. We instrument and automate written scripts and codes using TensorFlow. Then, we embed it into the software code for performance reports and spin up more Kubernetes clusters using that. We have separate templates or bundles and create them with the JAR files at the back to drive them.

Tomcat has the easiest application server to deploy.

Overall, I rate Tomcat six and a half to seven out of ten.

The solution is used for simple applications.

The product is easy to use.

The stability must be improved.

I have been using the solution for a couple of months.

I rate the tool’s stability a seven out of ten.

The tool is scalable. Large companies and banks are using it. We didn’t need to scale much. Two people are using the solution in our organization. We need two people to maintain the solution.

The setup is straightforward. The deployment took half a day.

We deployed the product in-house.

The tool is free.

I would recommend the solution for small applications. Overall, I rate the solution a seven or eight out of ten.

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.

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.

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.

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.