Tomcat Reviews

We use this solution for our website. When we have to integrate applications like scheduling tools with the website, we use Tomcat. We also use Tomcat to configure the applications that we have with either Automic scheduler or the D-Series scheduler.

The ease of use of Tomcat is its most valuable feature. Once we grade particular software, we simply download it and we keep an eye on if Tomcat is working. We have a link within Tomcat that tells us whether is working or not. 

Sometimes we face issues with the private and public networks and ensuring that once Tomcat is installed, that it is secure. This is an area of the solution that could be improved, possibly by adding an additional package for security. 

I have been using this solution for a few months. 

This is a stable solution. When we have experienced any issue, restarting Tomcat or completing an update has fixed the issue. 

This is a scalable solution. 

We have not needed to reach out to Tomcat for support during the last six or seven years. When we have had an issue, we have been able to resolve it on our own. 

The initial setup is really straightforward. Deployment takes between two and five minutes. If you are using Unix or Windows, you can click on the Tomcat website and you can download it from there. It's a very simple method and you can start and stop any time. If there is any problem, you can see the logs to understand what the issue is. 

I would recommend this solution to other businesses. It is important to understand what approach you are going to take when it comes to installation. Tomcat is user friendly compared to solutions such as WebLogic or Oracle. 

I would rate this solution an eight out of ten. 

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.

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

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.

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 primarily use the solution on our main e-commerce web page.

Compared to Oracle Web Projects, it's very user-friendly and the administration is very simple. The navigation is very intuitive.

The deployment process is very fast.

The solution is very stable. 

I don't have too much experience with monitoring, however, it's possible it could be improved. It would be great if they offered more integration of monitoring tools.

The management maybe can be improved a bit. 

I've used the solution for a small instance in the past. We have used it for three or four months now in a bigger instance. We've only used it for a few months at this point, and therefore, it's still pretty new to us.

The stability is good. We haven't had any issues. There are no bugs or glitches. it doesn't crash or freeze. It's reliable.

The scalability is good. We have a structure that we can easily scale up or down. It's very simple for us.

We haven't contacted technical support. We haven't needed any assistance. Therefore, I cannot speak to how helpful or responsive they are. 

I've also used Oracle WebLogic. 

The initial setup is very easy to install. It's very easy. A company shouldn't struggle with the setup process.

The deployment is fast.

I don't have any information on the pricing. I don't handle that aspect of the solution.

That said, my understanding is it's less expensive than, for example, Oracle.

I'm able to compare WebLogic with Tomcat, and I can say that Tomcat beats WebLogic on a number of fronts. It's easier, simpler to deploy, and less expensive. I prefer it. 

We're just customers and end-users. We don't have a business relationship with Tomcat.

We also use the solution on a private cloud as well as on-premises.

I'd rate the product at an eight out of ten. We're pretty happy with it.

I have experience with WebLogic and Tomcat. I'd recommend Tomcat over Oracle, as it's easier to manage and install. It's my understanding that the pricing is a bit lower as well.