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.

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.

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.

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.

We use this solution for our website. When we have to integrate applications like scheduling tools with the website, we use Tomcat. We also use Tomcat to configure the applications that we have with either Automic scheduler or the D-Series scheduler.

The ease of use of Tomcat is its most valuable feature. Once we grade particular software, we simply download it and we keep an eye on if Tomcat is working. We have a link within Tomcat that tells us whether is working or not. 

Sometimes we face issues with the private and public networks and ensuring that once Tomcat is installed, that it is secure. This is an area of the solution that could be improved, possibly by adding an additional package for security. 

I have been using this solution for a few months. 

This is a stable solution. When we have experienced any issue, restarting Tomcat or completing an update has fixed the issue. 

This is a scalable solution. 

We have not needed to reach out to Tomcat for support during the last six or seven years. When we have had an issue, we have been able to resolve it on our own. 

The initial setup is really straightforward. Deployment takes between two and five minutes. If you are using Unix or Windows, you can click on the Tomcat website and you can download it from there. It's a very simple method and you can start and stop any time. If there is any problem, you can see the logs to understand what the issue is. 

I would recommend this solution to other businesses. It is important to understand what approach you are going to take when it comes to installation. Tomcat is user friendly compared to solutions such as WebLogic or Oracle. 

I would rate this solution an eight 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.

Tomcat is a web server whose main facility is to have a web page.

The setup is complex and could be improved.

Stability depends on the requirements of the hardware assets. It also depends on how many users are on the web page and for how long.

The solution is scalable.

I used NGINX before Tomcat.

The initial setup was complex. It took two hours to set up the solution. Some SAP application was also involved during the setup.

When deploying the solution, we installed the host on the Linux server, followed by some basic configurations. In user management, there is an admin and a manager.

We don't have to pay for a license to use Tomcat.

I rate Tomcat a ten out of ten. I recommend that anyone choosing the solution use Google to find out what to do.

We use Tomcat as an application bucket for our Linux and Windows environments.

The product's pricing needs improvement.

I rate Tomcat's stability a nine out of ten.

We have 500 Tomcat users in our organization. It is a scalable platform. We plan to increase the usage.

We used Red Hat before.

The product is straightforward to set up. We have deployed it in a production environment. It took three years to complete. The process was executed by a team of ten technical executives, including engineers and developers.

We implemented the product with the help of an integrator.

We have purchased Tomcat's yearly license. It is an expensive product.

I recommend Tomcat to others and rate it a seven out of ten.