Tomcat Reviews

We use Tomcat for various purposes, and our company finds it to be perfect; we are getting all the solutions out of that. There is still no chance of any migration to any other technology, but additionally, we are looking into Apache Kafka to replace our Azure Service Bus.

We are using Apache server in one of our web applications and we also work with other Apache products, for example, ActiveMQ.

The Apache solutions we are primarily using now include Apache Tomcat Server, which is the web server.

The most valuable features of Tomcat for managing web traffic are evident in the web application that we are running on Apache Tomcat.

The advantages of Tomcat include its flexibility; we can increase the heap memory and the size of sessions as per our custom needs. We find it very familiar, simple, and robust, and these are the features we are still using in Tomcat.

Regarding improvements in Tomcat, I personally haven't used it very extensively, but all Apache products are very useful for our web applications. Although the web server setup is a little different, it has everything we have been using, and as of now, everything is good with no deficiencies that need improvement.

I think that Tomcat needs a more robust logging error details feature; the current logging feature is available, but it should be more user-friendly.

This improvement would make error handling more user-friendly.

I have been using Tomcat for about 10 years now.

The stability of Tomcat is good; we have not found any significant issues in recent days.

Tomcat is scalable because if we use our Azure platform, then it is scalable.

For maintenance, we don't maintain Tomcat directly; we contact Apache helpers for any solutions we need. They are proactive in looking into the tickets we create in case we have unresolved queries.

The technical support from Apache is responsive; if we have any ticket, that prompts a response, but simply posting in the forum may not get noticed by the team.

Posting on a forum is not very effective to solve issues.

If I were to rate technical support from Apache, I would give it eight out of ten.

Positive

It is very simple to install Tomcat; there are no challenges. Some process knowledge and setup in applications are needed. As I mentioned, we need to increase the heap memory of the size of the application, and it is very customizable, allowing us to use this application easily and meet our needs.

We have indulged into an AI platform as we have many more initiatives within our project. We have automated the logs of the future, using Elasticsearch for logging into the server's logs to automate the process of finding errors. We have implemented a solution for identifying errors automatically, and we are also looking into AI models for core help.

I rate Tomcat nine out of ten.

I work with Tomcat as a programmer, but not as an administrator. My major use case involves using Tomcat, mostly enclosed in any Java image for a Java application for REST API.

I do not work with the product as a customer, partner, service provider, or seller. Apache is a product that is used in any case. If you are using any API gateway, that could also be part of Tomcat that you are using as a programmer or API programmer. Tomcat is included in those scenarios. As a programmer, I define the ports and maybe define some security, but that is all. There is nothing about CI/CD pipelines for independent deployment of applications into Tomcat. The word is a little different now than it was 10 years ago when I worked with Apache as an application server.

Tomcat brings the biggest benefit through its simplicity. It is not just simple in terms of interface; it is simple for managing or very quickly running this server.

Tomcat's simplicity is very valuable, and the metrics I track to measure Tomcat's performance during high concurrency are mostly basic compared to other products or commercial products.

Tomcat lacks a visual tool for configuring. Everything is from the command line. I would like a visual tool for configuration to be added to Tomcat, as I see this feature missing.

I have been using Tomcat for more than 10 years.

Tomcat is stable and might not have some glitches.

Tomcat is easily scalable.

Everything regarding technical support from Apache is in the documentation or in some discussion portal. I never needed technical support.

I have used something similar to Tomcat, like Jetty. I don't see many differences between Tomcat and Jetty from a technical standpoint from my perspective as a developer.

The installation and deployment of Tomcat is just unzip and running.

On-premises deployment is possible. On-cloud deployment is also possible; this is just a click on that and that is all.

Developing any kind of web application server is time-consuming and expensive, and I can use Tomcat as a commodity, which is an existing tool that everybody uses.

I never calculated the ROI in percentage terms because nobody prepared a business case for what it means to build Tomcat.

I am familiar with pricing for Tomcat. For me, it is open source. Since it is open source, I don't see any fee for that regarding whether the license for Tomcat is usually expensive or quite affordable.

Tomcat is mostly used as an application server, not so often as a load balancer.

I mostly work with Kafka and just tried Amazon MSK, but not in production.

Apache Tomcat is capable of connecting to LDAP for validation of user roles if required. Everything is possible with securing the transport via TLS. There is a capability for protecting administration via the configuration, but I think that is mostly there is everything. I am not sure about encrypting passwords in the properties or if this is already added into Tomcat.

I have not yet used Tomcat's TLS virtual hosting feature and seen benefits from it.

On-premises deployment is possible. On-cloud deployment is also possible; this is just a click on that and that is all.

I would rate this review as a 9 overall.

We use Tomcat as an application server to deploy our developed applications. It's used for deploying applications on Tomcat servers and is suitable for small, lightweight applications.

Tomcat is a lightweight application server, which makes it easy to deploy and install small applications. It's particularly advantageous for microservices due to its simplicity, and it's useful as a starting point for those wanting to learn about application deployments. 

This tool is better for minor applications, although there are concerns with handling larger, memory-intensive applications.

Tomcat's stability could be improved, especially when handling more memory-intensive, large-scale applications. It tends to break and requires restarts with such applications. This can be difficult to manage. Enhancing its capacity to manage bigger applications would be beneficial.

Tomcat has been used for more than 15 years in our work.

Tomcat is stable for microservices and small applications. However, for large applications, the stability is low, and it doesn't suffice for memory-intensive operations, as it breaks sometimes and requires restarts.

Tomcat is scalable. We use embedded Tomcat in Spring Boot applications. For microservices, the scalability is quite effective. I would rate the scalability as eight out of ten.

We haven't used Apache support directly. We rely on search engines and forums for any support required.

Positive

The setup is very easy. I would rate it ten out of ten due to my extensive experience deploying Tomcat.

Tomcat is free to use as it's open source, so no setup cost or licensing fees are involved.

For more advanced need than Tomcat could provide, we have used Oracle WebLogic Server or other similar advanced application servers.

Tomcat is a suitable choice for deploying microservices or smaller applications. For beginners, it's excellent due to its lightweight nature and ease of deployment. For those dealing with larger applications, considering an alternative like Oracle WebLogic Server may be beneficial. 

Overall, I rate this solution eight out of ten.

I use it to deploy applications built with Spring Boot and Java. 

Tomcat is installed on-premises. Then, we expose what we call the management console. Developers can log in to the management console and do deployments from there.

I like the flexible nature of Tomcat. It allows you to deploy so many applications within a single instance of Tomcat.

Moreover, Tomcat's ease of use has positively impacted project timelines. Tomcat already has high availability – it doesn't go down so often and doesn't require a lot of maintenance. As long as your application works, you can depend on Tomcat. 

The integration with key databases like Redis and MySQL, as well as tools like RabbitMQ and more, is invaluable. Tomcat is a one-stop shop. You can easily connect to so many other resources that you need for a running system. If I were to summarize it, Tomcat is already a robust, quote-unquote, container for running a Java application.

For now, it fulfills all my integration requirements. 

Tomcat could be a little bit more innovative. Tomcat could come up with a framework that's more lightweight and purely targeted at Java applications. Some other solutions are doing better right now, maybe because they have come up with MicroProfile, which I think is moving forward. It may actually beat Tomcat because of the lightweight nature of the framework, the MicroProfile. They're coming up with new solutions. 

So, for the future of Tomcat and to maintain the market share they might be looking for, they need to come up with initiatives to ensure that several of us have a lightweight framework to deploy applications on.  

I have been using it for four years. 

Tomcat has high stability. That's one of the reasons I like it – I build an app, deploy it, and it just runs. That's the kind of independence I want.

It's very scalable. We currently have about a hundred engineers using it.

We've never needed tech support.

The initial setup is straightforward. We can do it in one to two hours. 

For the deployment process, you download the zip file from the documentation page, copy it to a server, unzip it, configure certificates, ports, and users, and you're ready to go.

Tomcat is flexible. You can deploy it on-premises with your own server and storage, or you can embed an IP version into your application and publish it on cloud platforms like AWS or GCP.

Tomcat doesn't release upgrades very frequently. Right now, they're working on version 11, but version 10 has been out for over a year. This means I can stay on version 10 for a while, and if I want to upgrade, it's straightforward. I simply download the active apps for the new version, set it up, decommission the old one, and I'm running with the new setup.

The main benefits are scalability and availability. Tomcat offers this. 

You don't need a high-end server. A server with 4GB RAM, 24GB storage, and maybe 20GB of additional disk space is enough to set up your Tomcat instance. 

This means your infrastructure costs can be low – probably under $100 USD per month if you're starting out. 

This means Tomcat won't impact your revenue much, and your return on investment (ROI) can be achieved quickly. With AWS, costs will be based on traffic, memory usage, CPU usage, and so on.

It's open-source. We don't pay for the license. 

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

There are several application server options: JBoss, WebLogic, Tomcat, and Payara. I've personally worked with all of them. 

I recommend Tomcat for on-premises deployments because I've found issues with WildFly – they have frequent releases and patches, and some become incompatible with existing setups. 

My advice is to go with Tomcat for on-premises setups. Also, if you want to move to AWS or GCP, it's easy. You just need to change how you compile your application; the application itself doesn't need to change. It's a matter of moving from a WAR (web archive) file to a JAR (JAVA archive) file.

I am using the solution at running level three. It is for running web applications.

I find the quick startup valuable, particularly the static quick startup. The server startup and application startup are very fast. I like that I can add any number of instances easily.

Resource configuration like JNDI and queue configuration, similar to other servers, should be provided from the admin console for Tomcat. Currently, it is done manually. The server config file must be edited. If a web interface were available, it would help me do it easily as an administrator.

I have used the solution for one year.

Sometimes, the server is not stable for long-running operations. I need to frequently restart it, like once every couple of days. The Tomcat instance must be restarted. Otherwise, it leads to memory issues.

I have not encountered any scalability issues.

On a scale of one to ten, I would rate the setup a ten.

It is simple to set up, and it won't take much time. You just use simple instructions and get started within a couple of minutes. 20 to 25 people, including developers and SRE people, can be involved.

There is no cost involved; it is completely free.

It has some manual configurations, however, for running simple web applications, it is definitely a go-to server. 

Overall, I would rate it a nine out of ten.

We use the tool for security. We use it to keep our applications on the web safe.

I like the solution’s ease of use. It is very easy to update certificates.

Our biggest challenge is that the Tomcat servers are not hosted locally. We have some contacts with companies that deliver the certificates to us.

I have been using the solution for two years. I am using the latest version.

I rate the tool’s stability a ten out of ten. I have never had any issues with it.

The scalability is really good. We never had any issues when we added new servers. It's very scalable. I rate the scalability a nine out of ten. We have more than 1000 users.

We never had any issues with support. The support team responds very quickly and solves all our issues. The support personnel are very professional.

Positive

The tool is deployed on the cloud. We do maintenance when certificates need updating, but we don't do the maintenance of the servers. We have about 20 engineers and administrators in our technical team. The deployment was very simple. We got a guide from Apache. Everything was explained very clearly. The deployment took a couple of days.

I will recommend the product to others. Overall, I rate the product a nine out of ten.

I use the tool for my Java application. It helps to deploy our servers. 

The solution integrates smoothly with the development environment. The integration process is straightforward. You only need to configure the project in your IDE. With intelligent features, the integration becomes even easier. Once integrated, deployment into our application is straightforward. Previously, we sometimes relied on manual deployment processes or used a separate application manager. However, with this solution, deployment is simplified. 

The solution loads quickly compared to other servers and is lightweight, resulting in faster startup times. Additionally, it consumes fewer resources, providing more flexibility. It also benefits from a strong community and documentation. Overall, it's easy to use and configure.

Tomcat needs to improve its user interface. 

I have been using the product for two and a half years. 

I rate the tool's stability a nine out of ten. In terms of stability, it's pretty stable. It's a live data application with a lot of functionality, which makes it easy to use and understand. However, there may be some issues with the version of Tomcat that need upgrading, which I need to address for the entire community's benefit.

My company has 40-50 users. A team of 35 resources maintains Tomcat. 

I haven't contacted the technical support directly. 

Tomcat's deployment is easy. However, the exact time it took varied depending on the complexity of the modules being integrated. For example, if a module contained more than 50 APIs and we were integrating only a portion of them, it naturally took longer than usual. The deployment can be completed in four to five minutes. 

The deployment process involved several steps. After completing the coding, we utilized Sourcetree to merge the code into our Git repository. From there, we deployed it onto our Jenkins server. We also tested the APIs. 

I believe it's a one-time expense for any company using Tomcat, and they're considered one of the best service providers. Acquiring Tomcat benefits businesses in many ways because it eliminates the hassle of managing servers. After implementation and integration, it becomes an automated procedure, making it simple and easy for businesses to use.

The tool's ease of use didn't pose any problems for us. We felt that it didn't cause any delays or issues with extending the timelines. Any delays were mainly due to vendor dependencies rather than issues with Tomcat. 

As far as security is concerned, an integrated team is responsible for it. As a developer, I believe it's pretty secure because it utilizes two modules running on different ports. Each application, one on Tomcat and the other on local, operates independently without interfacing.

I rate the overall product an eight out of ten. A dedicated team within our organization managed the Tomcat version upgrade. They were responsible for upgrading Tomcat. They didn't encounter any issues during the upgrade process. 

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. 

We use the product to deploy Java applications on Linux operating systems.

The product's most valuable feature is the ability to host applications.

Improvements could be made in the integration process of securing the Tomcat server within development environments like STS and SCS. The current procedure appears complex and could benefit from a more straightforward solution.

We have been using Tomcat for three years.

I rate the product's stability a ten out of ten.

We can host multiple web applications on IP addresses with Tomcat. We have 300 to 400 users working with it.

We used NGINX before. Our developers prefer Tomcat as it is easy to implement.

The initial setup process is straightforward. It takes 15 minutes to 20 minutes to complete.

It involves creating a JAR file to deploy a Python application. Once generated, this file must be placed in the designated location within the Tomcat server. Following this, we need to restart it, and the application is automatically hosted.

Initially, a developer codes the application, which then undergoes scrutiny by a senior developer. Later, a code review team verifies it.

We implement the product in-house.

It is an open-source tool and is free of cost.

The product is easy for expanding multiple web pages, installation, and implementation. I rate its performance a ten out of ten.

It provides good integration with other tools and software. The platform enables security features for various components, including servers, log directories, catalyst policies, and XML files. It helps us configure them in a way that no attacker would be able to view any of these files.

Overall, I rate Tomcat a 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.