Tomcat Reviews

My company uses Tomcat, which offers good features like servlet and JSP support. Tomcat is an open-source tool, and its community support is also good. Tomcat is a lightweight tool in nature, making it efficient in terms of memory and resource usage, allowing for optimized resource usage. Tomcat is a tool that can be embedded in other applications, allowing flexibility and deployment options. The security features of the tool are good. Tomcat offers good features in terms of cluster support, configuration, and maintenance.

Performance optimization is an area of concern in Tomcat that should be made better. I think the performance optimization has to be improved for monitoring, management of logs, load balancing, and containerization support. I think there is a need for some enhancement in the product's security as I work in my company's security area. If someone asks me about Tomcat from a performance perspective, I would say that tuning thread pools, caching, and compression needs improvement. In general, Tomcat should provide regular updates with respect to security.

I think Tomcat is a good and lightweight tool, but it needs improvement in areas like security and performance. Maybe a web application firewall or WAF products can be considered to protect the applications on websites, which is again some improvements needed from a security perspective. If you ask me about the feature and monitoring and management of logs, which are generally areas related to APM, needs improvement. Even the alerts provided by the tool need improvement.

Some simplified configurations and enhanced clustering can be considered for improvement in the product.

I have been using Tomcat for a few years. My company is a user of the product.

Considering that the product's performance and security need to be improved, I rate the solution's stability a seven to eight out of ten.

There are no issues with Tomcat's scalability. Scalability-wise, I rate the solution an eight out of ten.

I think a few hundred people use Tomcat for multiple projects.

The solution's technical support is good. I rate the technical support an eight out of ten.

Positive

Though I have experience with Jetty, Wildfly, and GlassFish, I feel that Tomcat offers users a better product.

The product's initial setup phase was simple.

The solution is deployed on an on-premises model. My company plans to deploy the solution on a cloud-based model for our clients.

In my company, we follow the right documentation we get from Tomcat, which allows us to get the right set of results and helps us with the product's installation and integration areas. My company generally doesn't have to depend on external help for the product's installation phase as Tomcat's documentation is good.

For some of the projects, my company needs to use the licensed version of Tomcat. My company cannot always depend on the free version offered by Tomcat.

I rate the product's price an eight on a scale of one to ten, where one is a high price, and ten is a low price.

I rate the overall product an eight out of ten.

Most microservices developed in Java are based on the Spring Boot framework, which ships Tomcast as the application server for each microservice.

Tomcat is not like a standalone application server because its main end use is to ship microservices. We don't use it like a standalone server nowadays.

If Tomcat could support the driver's VIN, they can run natively without the GBM. Now, we can run what we call the native cloud application that doesn't require GBM. If Tomcat can support that, it's going to improve performance and backup.

I have been using Tomcat for more than ten years. It's now embedded in Spring Boot applications, and the most modern architectures are based on microservices.

I would rate the stability an eight out of ten.

I would rate the scalability a nine out of ten. The scalability now is mainly for microservices that run on Tomcat, which are shifted like containers, and the scalability of the containers is the same, independent of whether the server applications are from cards or other things. So, scalability for now is much easier.

The solution is suitable for small and medium businesses (SMBs).

I worked with JBoss WildFly. We chose Tomcat because it is already integrated with Spring Boot framework, that's its main strength. If I compare it to JBoss, which is still not mainly integrated with that kind of framework.

It is embedded now, so we don't have any integration to do because Spring Boot comes with it already. It's like one integrated environment with Spring Boot.

The deployment method can be on-premises and on cloud. 

I would rate the pricing a ten out of ten, where one is high price and ten is low price. The pricing is pretty low. 

I would recommend using this solution. Overall, I would rate the solution an eight out of ten.

We use the solution as a web server for web-based applications. We also build data containers using it. 

The solution is convenient. It is a comfortable and easy-to-use solution for my use cases. 

The product needs to have more updates. 

I have been using the product for ten years. 

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

There is no complexity in deploying Tomcat. 

We regularly upgrade to the latest versions of Tomcat and apply security patches to comply with the latest security aspects.

I rate it a nine out of ten. 

Tomcat is a server that we use for stand-alone applications and databases.

Tomcat is easy to handle, its installation process does not take much time, and its server speed is also very good compared to other servers.

Sometimes, the UI part does not run properly, or the server goes down.

I have been using Tomcat for two years.

I rate Tomcat ten out of ten for stability.

I rate Tomcat an eight out of ten for scalability.

I have often faced issues for which I had to connect to the IT team. Sometimes, the UI part does not run properly, or the server goes down. I need to raise a ticket to restart the server. They will give us user ID and password for specific members so that we can fix the server issue. We need to get permission from the network team or IT team.

Positive

Tomcat's initial setup is easy. You can also change the port number. Running two or more applications in the same console or ID can result in a conflict. If we change the port number, Tomcat can easily identify this and keep to the specified web page.

Tomcat is an open-source server.

The solution is lightweight and provides the high flexibility needed in any stand-alone application.

Overall, I rate Tomcat a nine out of ten.

I have used Tomcat as a developer. We have integrated multiple things with Tomcat using the multiple packages within it. I have used bits and pieces of Tomcat for multiple things in multiple ways. With Tomcat, libraries can be exported and imported, converting it into a JAF file. Tomcat can be used to explore things, starting with the server configuration.

The most valuable feature of Tomcat is its ability to export libraries into different instances so that I can use it not only in one application but in multiple applications.

Suppose Tomcat is segregating its own version to utilize it in a testing area. It will be useful if a direct report concerning a particular server configuration or application usage is readily available in the dashboard.

I have been using Tomcat for 13 years.

Tomcat is a very stable solution.

Tomcat is a scalable solution. More than 100 users are using Tomcat in our organization.

Tomcat's initial setup is very easy.

Tomcat's pricing is very cheap.

I would recommend Tomcat to other users.

Overall, I rate Tomcat ten out of ten.

I am using Apache Tomcat for development purposes, specifically for deploying applications both on a local system and in a cloud environment. It is used in the IT industry.

I find Apache Tomcat very popular since it is easy to manage at a basic level. I can manage a complete server application. It is easy to host applications, customize, and configure. Even if I don't have much technical knowledge, I can manage it as a developer. Its security value is also good. It is open source and lightweight, which saves costs.

I have no recommendations for improvements.

I have been working with Apache Tomcat for more than ten years.

I think Apache Tomcat is excellent in terms of performance and stability. It is a stable solution as it frequently releases upgraded versions and patches.

I believe Apache Tomcat is scalable. It is stable and easily adaptable for different environments.

I have never consulted the customer support or technical support of Apache.

Neutral

I have not used any other tool before working with Apache Tomcat for application deployment.

I would rate the initial setup of Tomcat as either a nine or ten out of ten in terms of ease. It is very easy to set up as it only takes a few minutes for deployment.

Apache Tomcat is open source, so there are no associated costs for licensing or setup.

I recommend using Apache Tomcat due to its open-source nature, lightweight design, and ease of installation and configuration. 

I rate the overall solution ten out of ten.

Tomcat is there in most vendor solutions, and people rarely agree to port it to JBoss. So, most business applications have it. Additionally, multiple banking solutions are using Tomcat. Also, the solution runs on Solaris, AIX, Windows, and Linux.

Since I don't have too much exposure to the solution, I cannot comment on the features I like the most in the solution.

Vulnerability is one of the areas that can be considered an issue in the solution. Apart from that, there are no other issues with the solution. Also, I cannot comment on what additional features and changes need to be made in Tomcat.

With the solution's community version, we always have some patches and bug releases. However, we cannot deploy it since the vendor doesn't certify the book fixes in the solution. In short, we cannot just use it in production and test it ourselves when the vendor does not certify it. If a vendor is using a Tomcat-based application, then the vendor should be prompt enough to fix the available bugs in that particular version, which is not the case in reality. Any vendor who releases a product on Tom Cat should keep revising the version of their product based on the latest available bug-free version. These are some of the areas which can be challenging for those using Tomcat.

I have been using Tomcat for a long time now. So, it is not a new thing. Previously, the only concern in our organization was that we were stuck with open-source Tomcat. Before, Tom Cat was available in Red Hat's version, which got removed later. Now, they have packaged it under JBoss. Currently, it is a challenge for us to maintain the solution as an open-source tool.

Our company doesn't face any stability issues while using Tomcat. The only challenge we face using the solution is the bug-fixing scenario. So, when the security does a scanning, especially vulnerability scanning, we get into trouble. The vulnerability scanning points out a lot of bug fixes. Also, the vendors are not ready to test, or they don't give us testing results in a timely manner. Since it remains a pending issue, specifically the vulnerability issues, we cannot close it on time since it is on an open-source platform. The open-source community has introduced a patched version, but when a company uses Tomcat, the vendor may not be prompt enough to certify it with the latest patches and bug fixes.

The number of users can vary greatly depending on the specific product they opt for, and since I don't have an inventory for all the products that users are using, I cannot comment on the numbers. Generally, there are both back-office users and customer-facing users in most solutions.

Speaking about scalability, we use NGINX in front of Tomcat.

I won't be able to provide a rating on the scalability of the solution since we don't have a requirement in a company to scale up as of now. Also, we don't see such uses in our company wherein we have to consider a need beyond the four people who use the solution in our company.

There is no technical support since it is an open-source solution. In our organization, we attempted to secure paid support, but we were unable to reach a consensus internally to move in that direction.

In our organization, we use IBM WebSphere.

The solution's initial setup is straightforward since it is a file-based configuration.

Steps in deployment involve installing the product and then copying the configuration.

If it is a community version of the solution, no payment is required. However, if it is a Linux version, we must buy the solution from JBoss.

In our company, we always favor products like IBM WebSphere as it is a vendor product for which we get the right amount of support we need. Also, we are using IBM WebSphere on AIX. Hence considering our use cases, we feel that IBM WebSphere is a more stable and reliable platform. So as a critical system, we are using the aforementioned solution. We use Tomcat in a company when we have no other options and are forced to use it, especially in scenarios where no other platforms are supported. So, if we have an option in our company, then we keep the usage rate of Tomcat low. Overall, I rate the solution a six out of ten.

Tomcat is actively used, and there are many more instances like it. Numerous sites using this application server, which is relatively easy to set up. I can use JBoss or any other deployment tool that is available, but I mostly use some technical tools for this purpose.

Tomcat is a single-server solution for deploying applications that can scale effectively. It's a good choice because it simplifies deployment. Once you package your application, deployment is straightforward and efficient.

If you have multiple tasks, you definitely need different ideas. However, if you only consider the deployment of an application to a target server, it’s mainly about the technical performance. There might be some challenges because it’s only a website, but the server should solve the issue. You deploy the website there, and sometimes you might need multiple servers.

I have been using Tomcat for eight years.

The solution has good support.

Spring Boot is the most commonly used development tool, everyone is using Tomcat, which comes bundled with Spring Boot. Spring Acura comes with a Tomcat category.It provides a good UI and makes it more applicable as long as the client resources are accessible. There is no difference; we're using a single port. Anybody can assign a port number to it. You cannot change it to your firmware, but you can change it.

To deploy an application in Tomcat, you simply need to install the software, navigate to the deployment directory, and place the WAR  or JAR file there. Registering the server is then necessary. The time required for deployment depends on the size of the WAR or JAR file. It's better to place the file in the appropriate directory for your specific product. Be aware that the deployment time can vary, in a SaaS environment. Generally, deployment times are quick, but this can change based on the application.

I'm using both Tomcat and GlassFish.

When declaring the application, the springboard is ready for use with Apache Tomcat. By default, it comes this way when you unplug it from Git. So, when you are deploying any application, it uses Apache Tomcat by default.

One engineer is enough for the solution.

In data centers, we need to analyze the backlog. You need a cost analyst to determine if integration or migration is necessary. Both are important for identifying requirements. Once you have clarity on these points, you can proceed with management. If these factors are achievable in the decision-making process, then it's worth considering.

Overall, I rate the solution a ten out of ten.