Tomcat Reviews

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.

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.

Our company uses the solution as a web server for hosting items. Anyone in the world can access website that is hosted on top of the solution. 

We implement the solution for customers in banking, investment banking, and government. All of our customers host with the solution. 

The solution is very, very fast and provides immediate website availability around the world. 

You can host any compatible website. 

The solution has very robust functionality. 

The solution cannot host .NET applications. 

I have been using the solution for eleven years. 

The solution is stable. 

The solution is very scalable and you can add any number of applications on top of it. 

The solution is open forum so it is difficult to get technical support if you need it. We don't really require technical support. 

The setup is straightforward and very easy. 

We implement the solution for customers. Deployment takes a couple of hours depending on use case. 

If you are deploying for normal users, then deployment will take a maximum of five or six hours. If you are deploying for direction users, then deployment will take eight or nine hours. 

First, you need to get the binaries for the server. Once the binary is optimized, you need configure your server to optimal size based on your requirements. Then, you quickly start your server using the startup and do any stacking. 

One developer good at JAVA and two developers good at networking can completely deploy and manage the solution for customers. 

The solution is open source so is free. 

I definitely recommend the solution for website hosting. I rate it a seven out of ten only because customer support is not available. 

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.

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.

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 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's best feature is the open source server.

It's a flexible and lightweight solution.

Tomcat is not user-friendly. I would also like to be able to have multiple applications run at the same time.

In the next release, I would like to see better security features.

I've been using this solution for more than six years.

It is stable.

Tomcat is a scalable product. More than 100 people use it in my company.

The technical support is good, and I rate them at eight out of ten.

Positive

The initial setup is very easy.

Tomcat is an open source solution.

On a scale from one to ten, I would give Tomcat an eight.