Tomcat Reviews

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

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.

Our company is in healthcare, and Tomcat provides a backend server for our REST solution. Tomcat is widely used in Chile as a backend solution for web service and REST environments. Companies frequently use Spring Boot with a Tomcat environment. I'm a developer at a small company, and only 10 people use Tomcat here, but the company has around 100 employees in all. 

Tomcat is a simple, light environment, whereas the full Red Hat Fuse solution is heavier. 

Security integration in Tomcat is complicated. We need to use another tool to solve the security issues.

We have used Tomcat for two years.

We have some problems with the performance in terms of transactions per second, but Tomcat is stable.

It is easy to scale the solution if you use more CPUs.

Tomcat is an Apache open-source project, so it doesn't have technical support. 

We were using Red Hat Fuse for a Camel solution. Camel is another Apache product we use internally.  Two years ago, we switched our backend solution.  I was working with a bank, and we needed an integration platform. It was a relatively simple project.

Deploying Tomcat is straightforward.

Tomcat is a free solution, but you need to pay the Java Oracle license in a commercial environment.

I rate Tomcat eight out of 10. My only issue with it is the security. You need to use another solution.

We primarily use the solution on our main e-commerce web page.

Compared to Oracle Web Projects, it's very user-friendly and the administration is very simple. The navigation is very intuitive.

The deployment process is very fast.

The solution is very stable. 

I don't have too much experience with monitoring, however, it's possible it could be improved. It would be great if they offered more integration of monitoring tools.

The management maybe can be improved a bit. 

I've used the solution for a small instance in the past. We have used it for three or four months now in a bigger instance. We've only used it for a few months at this point, and therefore, it's still pretty new to us.

The stability is good. We haven't had any issues. There are no bugs or glitches. it doesn't crash or freeze. It's reliable.

The scalability is good. We have a structure that we can easily scale up or down. It's very simple for us.

We haven't contacted technical support. We haven't needed any assistance. Therefore, I cannot speak to how helpful or responsive they are. 

I've also used Oracle WebLogic. 

The initial setup is very easy to install. It's very easy. A company shouldn't struggle with the setup process.

The deployment is fast.

I don't have any information on the pricing. I don't handle that aspect of the solution.

That said, my understanding is it's less expensive than, for example, Oracle.

I'm able to compare WebLogic with Tomcat, and I can say that Tomcat beats WebLogic on a number of fronts. It's easier, simpler to deploy, and less expensive. I prefer it. 

We're just customers and end-users. We don't have a business relationship with Tomcat.

We also use the solution on a private cloud as well as on-premises.

I'd rate the product at an eight out of ten. We're pretty happy with it.

I have experience with WebLogic and Tomcat. I'd recommend Tomcat over Oracle, as it's easier to manage and install. It's my understanding that the pricing is a bit lower as well. 

I use Tomcat for CM solutions, for access management.

We chose to use Tomcat because it's perfect compared to other containers that we have tested.

It's open-source and there is a lot of documentation available on the web. It has a good knowledge base.

The interface is not user-friendly.

You need to have knowledge of the operating system, and Linux to configure the solution. It is not user-friendly.

I would like to see a user-friendly interface.

I have been using Tomcat for 10 years.

I started with Version 8 and now we are using Version 9.

The stability is amazing. If it is configured properly, you won't have any issues.

It's scalable. It is possible to create a cluster with Tomcat. You can run it using Docker, in the Kubernetes platform. It is also possible to be embedded in some devices.

It's pretty much a full-stack solution with many ways to use it.

We have 30 technicians who are using this solution in our organization.

I have never used support from Tomcat. We have only used the documentation that is available.

There is a lot of documentation available on the internet, which is very helpful.

We have found a solution for questions that we have had through forums and the knowledge base.

The initial setup is neither hard nor too easy. There is a lot of documentation to review.

The time it takes to deploy really depends on your experience. If you are a beginner, it can take eight hours, and for the heavy user, it's about two hours to deploy it.

We are using the open-source version.

Read the documentation that is available on Apache.org. If you have any issues, look to see what is available on the forums and on the web.

Some people have been able to find a solution using the web.

We have not had big issues when using Tomcat. I would rate Tomcat an eight out of ten.

We are using Tomcat for one Java-based application that's used for any carrier site. We have one portal for carriers. Any external user can apply for whatever openings are there. Through that site they can apply and our HR can review their profile and invite them for an interview. Tomcat is handling all these processes.

The company decided earlier, when our database was on Oracle, that Tomcat is more suitable for Java-based applications and it's a free tool with free servers that we can download and use there.

Tomcat is user-friendly and easy to set up, especially compared to WebLogic or JBoss where some specialty is required. If you are going for Tomcat, you can use their guidelines and can set it up easily

Tomcat is used mainly for database connections. As of now, we configure that environment for any database configuration. But if any utility can integrate where we can pass the database connection as a string of details, then it should encrypt them and keep them inside. From that security perspective, Tomcat requires improvement. They should integrate this security feature.

I have been using Tomcat in my company for the last two years. In my previous company I used Tomcat for application, deployment and configuration.

Tomcat is very stable, nothing new in this one, it's a very old product. We were using this product for our small application testing back when we were in college.

In terms of Tomcat's scalability level, wherever scalability or a higher ability is required, we use a load balancer and other things to just upscale the data.

We have one 15-person team that is using it. It is exported to the internet, so external users are using it whenever they connect to the application.

We provide technical support because we have the knowledge about this product so we don't feel any external support is required as of now for Apache and Tomcat related issues.

The initial setup is very easy and straightforward.

It takes me a couple of hours for Tomcat implementation.

Tomcat is an open-source solution so we don't have licensing costs.

My advice to someone considering Tomcat is that they don't have too much load on their website. It's not for all websites. For normal sites, they can use Tomcat.

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