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.

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

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.

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

It's a rock solid Java host.

It is at the core of our production application server environment.

None that I can think of.

I've been using it for 10 years,

No, it's rock solid.

The server needs to be bounced every three months. We reboot on schedule whether we need to or not.

No issues encountered.

It's open source and the community is very helpful.

It's open source and the community is very helpful.

We used IBM WebSphere, but the cost drove us to Tomcat.

It's drop dead easy.

We did it all in-house.

No investment, and a huge return.

We bounce the servers every three months, but other than that the costs are trivial.

We looked at other products from IBM, Sun, BEA and a couple others.

Do it. Drop it in and if you have huge traffic requirements, drop it on a couple of machines and run a network balancer.