Tomcat Reviews

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.

The primary use case of the solution is for developing applications and installing applications on the web.

I prefer to deploy my Java applications on Tomcat, as it is free and provides excellent performance and solutions. Additionally, there are two or three more solutions such as JBoss and WebSphere from IBM, but Tomcat remains my preferred choice.

The most valuable feature is how simple it is to deploy the solution.

The disability and memory management is a problem with the solution and has room for improvement.

I would like to have quicker Java application deployments.

I have been using the solution for 20 years.

I give the stability of the solution a seven out of ten.

I give the scalability of the solution an eight out of ten.

The initial setup is easy and straightforward.

We have seen a return on investment with Tomcat quickly.

I give the pricing an eight out of ten.

I give the solution an eight out of ten.

Depending on the hardware an organization is using, there can be memory issues when using the solution.

Our primary case use is for case logs. When the customer tries to log into the application and the webpage does not open I check it from the integration of Tomcat.

I would like to see the APM tools enhanced for all customers. Some APM customers are not yet fully integrated. I would also like to see a dashboard with some integrations in order to see the logs and trace performance easier.

I have been using Tomcat for the past four years.

Tomcat is not always stable and but I have not used another server yet to compare the overall stability.

The scalability overall is good.

The initial setup is straightforward. The time frame of the deployment depends on configurations and parameters that a company may have.

We are currently using the open-source version.

I would rate Tomcat a ten on a scale of one to ten.

I have used Apache Tomcat for various applications in our operational environment. We are a traffic service provider, and our operational department needs various types of proprietary applications.

In our environment, Tomcat is reliable and secure. We don't have to make many changes, and the applications work as expected.

Tomcat is reliable and secure, which makes it valuable for our application deployment. We do not have to intervene much to make changes.

Perhaps there could be an easier way to configure some advanced features. The learning curve to earn advanced skills is too steep.

I have been using Apache Tomcat for more than ten years.

It is very stable.

Tomcat is scalable. I would rate it an eight out of ten for scalability.

I have never consulted Apache support.

Positive

Personally, I rarely work on Tomcat. However, if I had to rate the setup from one to ten, with ten meaning easy, I would rate it an eight.

Tomcat is completely free of charge.

I would recommend using Tomcat because it is simple to integrate and use.

I'd rate the solution nine 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 allows me to deploy my Java app servers. I use it very heavily as a Java server, and it also doubles up as a web server. So my web and application server gets serviced out there. Then, I have my reverse proxy in front and put the Apache web server. So that feeds the request across to the Tomcat servers, and the Tomcat servers service it. In Tomcat, I can write the JSP code that services the pages and embed my jQuery code, which will then look up the database at the back end.

I can set it up in a completely horizontally scalable Kubernetes cluster and drive that through. My cluster manager allows me to load balance, providing massive scalability. I can deploy a thousand app servers concurrently and very easily. That is the power of Comcast.

I love Tomcat for its scalability, reliability, availability, and steadiness. There are a lot of bots that come and hit and a lot of RPA codes that come and corrupt. RPA tools themselves create a lot of bugs because they come and try to instrument and automate a lot of things. The people who have written that code are not very up to the mark in terms of not messing with the app servers.

Sometimes, the app servers get corrupted, and then they hang. So, I should be able to instrument it in such a way that my Kubernetes cluster takes over and switches it to another app server, and it blocks the RPA from coming and touching it. I can do that with Comcast very easily.

Java has not been very good for some time in the middle, and then, again, they have improved. I have to ensure that the binary codes are compiled and set up correctly. I have to ensure the classes are done and the framework is correct. When I look at the classes, I need to be able to identify the entire framework correctly.

Therefore, I need to push it to the documentation framework, which will automatically take the software code and ensure the documentation is happening correctly. Java functions should be built better into the solution.

I have been using Tomcat for 15 years.

It takes around ten minutes to deploy Tomcat.

With Tomcat, it is very easy to spin up and deploy the instances. Managing and debugging the code sets saves a lot of time and money.

Tomcat and Apache have no user interface; we do it on the command line. We instrument and automate written scripts and codes using TensorFlow. Then, we embed it into the software code for performance reports and spin up more Kubernetes clusters using that. We have separate templates or bundles and create them with the JAR files at the back to drive them.

Tomcat has the easiest application server to deploy.

Overall, I rate Tomcat six and a half to 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. 

The solution is used for simple applications.

The product is easy to use.

The stability must be improved.

I have been using the solution for a couple of months.

I rate the tool’s stability a seven out of ten.

The tool is scalable. Large companies and banks are using it. We didn’t need to scale much. Two people are using the solution in our organization. We need two people to maintain the solution.

The setup is straightforward. The deployment took half a day.

We deployed the product in-house.

The tool is free.

I would recommend the solution for small applications. Overall, I rate the solution a seven or eight out of ten.