Tomcat Reviews

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

• It’s an open source software project, developed under the Java community process and the Apache license version 2.
• It has a big knowledge base.
• It works very well with web projects that have a low budget.
• Scalability
• Simple configuration files

In my organization we have lots of technologies and we use Apache Tomcat for web projects that don’t need the EJB implementation. We use it because it is cheaper than other products, and we have in-house knowledge of the topic. Actually, we have large-scale and mission-critical web applications running in Apache Tomcat with a reasonable budget.

This product needs an improvement to its centralized management console that can apply configurations and deployments for large scale clusters and groups of servers without the need of accessing each server to apply the changes. Also, it would be nice to have multiple profiles pre-configured for specific utilization, like other products in the market.

I have been using Apache Tomcat since the beginning of 2010.

If you have a nice development team, with best practices in mind and good code implementation technicians, everything will be OK.

You only need to test and monitor to find the correct set of configurations for your system or situation. Beware of this, and with patience and some criteria you will find the best set of configurations to stabilize your application in a short time period.

Same as above, you just need to test and monitor to find your needs to attend your system or situation.

There is no customer service, only the Apache Tomcat community, but there is a large knowledge base.

There is no official technical support for this product and you don’t find the solution at the community, then you need to acquire consultant services from the market.

Once, we had a big cluster that needed complex configurations and we changed our option and now work with JBoss 6 EAP from Red Hat. This was because it has a centralized management console for cluster configuration and to apply changes to all the nodes at the same time that’s simplified a lot our work.

Apache Tomcat, maybe the easiest and simplest Java Web Server on the market,as you just configure your environment and start it. The deployment depends on your needs, but it can be one server or a hundred, but if you don’t need the EJB implementation you can go without it. To deploy your application just go to the console or just copy the file to all the nodes from the group. It's really easy.

We always do implementations with our in-house teams. Our level of knowledge of this product is very high, and the community people always help with your project, or you just find the answer when you need.

To calculate the ROI of this product, it depends on your knowledge. If you have the knowledge in-house, it is just free, there is no investment, just the infrastructure you need to operate it and with the market there are plenty of nice cloud vendors. It's easy to find a solution on a budget.

If you don’t have the knowledge in-house, there are other vendors in the market that are Tomcat based and have other features like centralized management, modular functionality, customer services, technical global support, SLA and can fully attend the JAVA EE 6 and 7 specifications. For example, we have JBoss EAP from Red Hat, which is, maybe, the best correlation between price/performance/support at the market.

If Apache Tomcat works with your application and you have the knowledge, you can use it without fear. Just test, monitor and deploy.

If you don’t have the knowledge in-house, there are other vendors in the market that are Tomcat based and have other features like centralized management, modular functionality, customer services, technical global support, SLA and can fully attend the JAVA EE 6 and 7 specifications. For example we have JBoss EAP from Red Hat, which is, maybe, the best correlation between price/performance/support at the market.

Tomcat is the best product in this category. If you have low budget and if you just need Java server pages, servlets and basic pages, it does the job. Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations, but always remember that you need to have in-house knowledge to work with it!

You don’t need to have fear. It is simple and efficient. Just search the community and you will find your answers.

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.

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.