Tomcat Reviews

We use Tomcat as an application bucket for our Linux and Windows environments.

The product's pricing needs improvement.

I rate Tomcat's stability a nine out of ten.

We have 500 Tomcat users in our organization. It is a scalable platform. We plan to increase the usage.

We used Red Hat before.

The product is straightforward to set up. We have deployed it in a production environment. It took three years to complete. The process was executed by a team of ten technical executives, including engineers and developers.

We implemented the product with the help of an integrator.

We have purchased Tomcat's yearly license. It is an expensive product.

I recommend Tomcat to others and rate it a seven out of ten.

Our primary case use is for case logs. When the customer tries to log into the application and the webpage does not open I check it from the integration of Tomcat.

I would like to see the APM tools enhanced for all customers. Some APM customers are not yet fully integrated. I would also like to see a dashboard with some integrations in order to see the logs and trace performance easier.

I have been using Tomcat for the past four years.

Tomcat is not always stable and but I have not used another server yet to compare the overall stability.

The scalability overall is good.

The initial setup is straightforward. The time frame of the deployment depends on configurations and parameters that a company may have.

We are currently using the open-source version.

I would rate Tomcat a ten on a scale of one to ten.

We developed a Java application, which was a content management application, and deployed it on the Apache Tomcat server.

We can use Apache Tomcat for Java server applications. We can use Apache Tomcat for application servers as well as web servers. We can easily deploy a Java project in Apache Tomcat.

Tomcat's cache could be improved. Tomcat's performance is less than other solutions like IBM WebSphere or JBoss.

I have been using Tomcat for nearly five years.

Tomcat is a stable solution.

Tomcat's initial setup is a little bit difficult.

Tomcat is not costlier than other solutions.

I would recommend the solution to other users.

Overall, I rate Tomcat a nine out of ten.

The solution is readily available and open-source. 

Tomcat needs to improve its stability. 

Tomcat is stable. 

I rate the tool's scalability a nine out of ten. 

Tomcat's installation is easy and takes 10-20 minutes to complete. You need to download the solution and install it. 

We can do the tool's deployment in-house. 

I rate the tool a nine out of ten. 

Tomcat's best feature is the open source server.

It's a flexible and lightweight solution.

Tomcat is not user-friendly. I would also like to be able to have multiple applications run at the same time.

In the next release, I would like to see better security features.

I've been using this solution for more than six years.

It is stable.

Tomcat is a scalable product. More than 100 people use it in my company.

The technical support is good, and I rate them at eight out of ten.

Positive

The initial setup is very easy.

Tomcat is an open source solution.

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

We use the tool to deploy Java applications. 

Tomcat is secure, reliable, and stable. 

Deployment in Tomcat should be done through a GUI. We deploy applications from the backend using commands.

The tool is stable. 

My company has 1,000 users. 

We often contact support if we encounter issues during application deployment. In such cases, we must contact the Tomcat support team for assistance.

The tool's deployment is easy and takes two years to complete. 

I rate the tool a nine out of ten. My advice for those looking to start using Tomcat is that it's a good choice. It's a secure, scalable, and stable product. While other products are in the market like JBoss and others, Tomcat stands out as a reliable option.

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.

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.