Tomcat Reviews

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.

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

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.