Tomcat Reviews

We are using Tomcat and we are making the configuration with the help of Spring Boot only.

Tomcat is cloud-based, and all the microservices are developed in Spring Boot.

One of the most valuable features of Tomcat is its compatibility with the Apache web server and its ease of configuration. It is simple to set up and maintain and allows for easy management of database connections, transactions, and isolation. Overall, Tomcat is a user-friendly application server that makes it easy to manage various aspects of database interactions.

Tomcat is running a lot of services and operating to my requirements. 

One way to improve the solution is by making the logging capabilities of Tomcat better by providing a logger within the server itself and making it easy to access and view the server logs. This can be especially useful when debugging issues with applications deployed on the Tomcat server. By having the ability to view both the application logs and the server logs, you can more easily identify the source of any issues and troubleshoot them more efficiently. Providing a connector or other similar feature that allows you to access the server logs from within your application can also be helpful in this regard. Having access to both the application logs and the server logs can be a valuable resource when trying to identify and resolve problems.

To make it easier to identify and troubleshoot issues, it can be helpful to have a single location where you can view both the application logs and the server logs together. This could include only the debug and error logs, rather than all logs, to make it easier to focus on potential issues. By having all relevant logs in one place, you can more easily scan for problems and identify their source, whether it is within the application or the server. This can save time and improve the efficiency of your troubleshooting efforts.

I have been using Tomcat for approximately five years.

I have not had a problem where the solution failed.

I rate the stability of Tomcat an eight out of ten.

We have approximately 70 people using this solution in my company.

I rate the scalability of Tomcat an eight out of ten.

Tomcat itself does not need any support. Everything is on the internet. Proper documentation is there. I have never tried to contact or ask for support from Tomcat. Wherever there is no support, it is the best support for a solution.

As the CTO, I compared Apache Tomcat with IBM WebSphere Application Server and Oracle GlassFish. In the end, I chose Tomcat because it is easy to understand, well-documented, and has a strong community of users and developers. It is also straightforward to debug any issues that may arise. Tomcat is a reliable and user-friendly choice for an application server.

One of the advantages of using Tomcat is the strong community of users and developers that provides a wealth of knowledge and resources online. If you encounter any issues or problems while using Tomcat, it is likely that others have experienced the same issue and have shared their solutions online. This makes it easy to find answers and get support when you need it. In contrast, IBM WebSphere Application Server has a smaller user base, so there are fewer discussions and resources available online to troubleshoot problems. Tomcat's widespread use and strong online community make it a reliable and supportive choice for an application server.

I find IBM WebSphere Application Server very difficult to configure and with Oracle GlassFish, there is no proper documentation.

Tomcat is best for my use case.

The initial setup of Tomcat is straightforward compared to other options on the market, such as IBM WebSphere Application Server. In contrast to IBM WebSphere Application Server, which can be difficult to configure, Tomcat has a user-friendly setup process. Additionally, Tomcat has a default configuration that is optimized for performance, making it a good choice for those who may not be familiar with configuration settings. The default values in Tomcat are set to the best configuration, ensuring that even those who are not experts in configuration can use Tomcat effectively.

The price of the solution is good.

I rate the price of Tomcat an eight out of ten.

While Tomcat is a reliable choice for an application server, it may not be the best option for real-time tasks involving TCP connections, WebSockets, and socket programming. In these cases, Netty may be a better choice due to its stability and performance. In your experience, you found that Tomcat was prone to connection issues when used for socket programming, leading you to switch to Netty. It is important to consider the specific needs and requirements of your project when deciding which tool or technology to use.

I rate Tomcat 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 cloud-based platform. Previously, deploying applications required setting up a Tomcat instance and then deploying the application on it. However, our solution has streamlined the process by prebuilding and prepackaging multiple services, each equipped with its own embedded Tomcat instance. This simplifies deployment, maintenance, and configuration tasks. Instead of managing separate instances for each application, we can now seamlessly deploy each application with its own embedded Tomcat instance in the cloud environment.

Tomcat has connectors like REST requests to connect the front end. Also, some parts of the inter-system communication go through REST. External connections with third parties occasionally involve both REST and SOAP protocols. Tomcat is versatile in accommodating these various communication methods.

We are using Tomcat primarily as a request blocker. It manages queues and handles routing. The size of these queues can be adjusted to scale the application, accommodating perhaps 50-100 REST connections. Using these tools, we achieve our scalability goals. Tomcat is a highly scalable solution.

Tomcat is a polished product that has been around for a long time. It should be simple and high-performing, with the ability to grow and maintain stability. The fewer features it has, the more stable it will be.

Also, there could be more configuration options. It's always lovely to have finely tuned-configurations.

I have been using Tomcat for many years.

The product is stable. I rate the solution's stability a ten out of ten.

The solution's scalability is impressive. We manage multiple ports for various systems; for instance, one of our systems utilizes eight ports. Consequently, we deploy the corresponding package eight times. Additionally, we employ a load balancer to distribute traffic across these eight ports, effectively managing incoming requests. Scaling horizontally involves utilizing updates, and there's potential for further scalability in this direction.

I have some limited experience with JBoss. Tomcat has become the standard now. There are other application servers like JBoss. They offer some excellent features for web projects. However, Tomcat is basic. Other servers provide more on top of that, which can be advantageous in some ways but also disadvantageous in others. They may be harder to support, have some issues, and be more complex.

Additionally, they might not scale horizontally as well. That was my impression maybe ten years ago. However, I believe Tomcat is now the de facto standard, and you'd need solid reasons to choose anything over it, perhaps for specific features that you can't find in Tomcat but might be available in other application servers. On the other hand, Tomcat is simple, quick, and scalable, making it a perfect solution.

The setup process is straightforward. Also, additional fine-tuning options are available in the application setup. Overall, it is a polished product. It has been evaluated over time and effectively meets our needs. Tomcat is pretty packaged together for deployment.

We deployed it in-house.

The product is free of cost.

We use it locally. It's really fast for development and very easy to deploy in production. We are using all of this with a single distribution. We have the same Tomcat version we use on our local machines, test servers, and production. Having this same deployment allows us to test it locally and on test systems before deploying it to production.

I suggest going with the embedded Tomcat, which is available with Spring. Let's say you use a job framework like Spring, incorporating Tomcat.

We have multiple web services, some accessible internally and others externally. We employ a set of firewalls to protect our internal services. Additionally, we use microservices for functionalities for external access. These functionalities are developed into separate, small web services and secured externally. The security measures, including firewalls and server-to-server access, are implemented independently of Tomcat within our setup.

The product is simple and easy to scale. Overall, I rate the product a ten out of ten.

I primarily use it for running Java projects.

It allows me to conduct all my testing and experiments fast and efficiently.

It's very robust and stable, which is valuable to me.

I have been using this solution for three years. 

It's very stable. No problems at all. I would rate the stability a ten out of ten. 

The scalability is quite good. I would rate the scalability a seven out of ten. I haven't had a chance to test it extensively in cloud-native scenarios like Elastic Cloud. 

I haven't tested it in the newer versions. They claim to support it, but I don't have any personal experience with it.

I'm the only one using it, primarily for testing purposes with JAVA Software.

It's quite simple, like any other software installation. The deployment takes only half an hour. 

I did it primarily in-house for testing purposes. You just need to copy the configuration files, and that's pretty much it. It's not very technical.

You can deploy it wherever you want. You can use it on-premises, in the cloud, or anywhere else. You're in control.

You don't need any special technical expertise to deploy Tomcat.

Tomcat is open-source and free to use.

There was no need for evaluation. Tomcat met all my needs.

You just need to keep it up to date with the latest Java Virtual Machine software, and that would be all.

Overall, I would rate the solution a ten out of ten. For anyone starting with Java development, I highly recommend starting with Tomcat. It might be an old-fashioned technology, but it's reliable and easy to use.

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.

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.

We use Apache Tomcat servers to host our Actimize application.

In terms of NICE Actimize, it is very useful. That said, it can host such wider options for such a heavy application. 

The GUI is smooth. Whatever configurations are required, they're compatible in terms of the Actimize solution, and they tend to provide the best experience for the user.

It is easy to set up.

The solution can scale.

It is stable. 

I've not used any other products in that space apart from the Apache versions. Having nothing to compare it to, it's hard to see what a weakness is. 

Some items may be vulnerable due to IT attacks or IT security breaches. If Apache can come up with a better solution to provide better security, that would be ideal. It is something that could be improved in both Apache and NICE Actimize.

I've been using the solution for my entire career. I've used it for more than nine years at this point. 

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. 

It's quite scalable. I'm aware that it's used in other applications as well, not just NICE Actimize. 

Most of the users are in IT support.

I've never reached out to technical support. 

I have not used a different similar solution in the past.

The solution offers a straightforward setup. While I have not done it myself, I'm aware that it's relatively simple. It's been hosted in the cloud in my previous project, and we have experience implementing it on Windows. 

I'd rate the ease of implementation eight out of ten.

I can't say how long it takes to deploy the solution. That's handled by another team. We just have a part of Actimize hosted on that server. That's it.

I do not deal with the pricing. 

I'm not sure which version of the solution we're using. It's likely close to the latest version.

Apache is well suited, at least for NICE Actimize. I'd recommend the product to others.

Based on the exposure I have, since it's limited to just one application being hosted or using Apache Tomcat, I would rate the solution seven 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.

Tomcat is a free and secure Linux-based application development tool. It can be deployed quickly in any environment.

The solution should develop a better UI base in the Linux environment.

Tomcat has a Linux environment and is available as a CLI-based system.

I have been using Tomcat for four years.

The product is stable.

I rate the solution’s stability an eight out of ten.

The solution is scalable. There is no downtime.

We’ve 10-15 people using this solution in our organization.

If we experience any bugs, the support team provides us with hard fixes or patching, and then we can troubleshoot them.

The initial setup is easy. We can directly download it from the website and install it.

I rate the initial setup a nine out of ten, where one is difficult, and ten is easy.

Tomcat is a free tool, but if you need any hard fixes or patches, the cost will depend on the type of support you need.

Apache Tomcat is a free tool. It can redirect or direct STDPs and other types of traffic. We are using a multi-level server setup.

It is a simple tool to install and configure. We can accommodate it because the Apache Tomcat Marketplace is available, which provides a free set of open-source plugins and components.

Overall, I rate the solution an eight out of ten.