Tomcat Reviews

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.

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 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.

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. 

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.

Our company is in healthcare, and Tomcat provides a backend server for our REST solution. Tomcat is widely used in Chile as a backend solution for web service and REST environments. Companies frequently use Spring Boot with a Tomcat environment. I'm a developer at a small company, and only 10 people use Tomcat here, but the company has around 100 employees in all. 

Tomcat is a simple, light environment, whereas the full Red Hat Fuse solution is heavier. 

Security integration in Tomcat is complicated. We need to use another tool to solve the security issues.

We have used Tomcat for two years.

We have some problems with the performance in terms of transactions per second, but Tomcat is stable.

It is easy to scale the solution if you use more CPUs.

Tomcat is an Apache open-source project, so it doesn't have technical support. 

We were using Red Hat Fuse for a Camel solution. Camel is another Apache product we use internally.  Two years ago, we switched our backend solution.  I was working with a bank, and we needed an integration platform. It was a relatively simple project.

Deploying Tomcat is straightforward.

Tomcat is a free solution, but you need to pay the Java Oracle license in a commercial environment.

I rate Tomcat eight out of 10. My only issue with it is the security. You need to use another solution.

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.

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.