Likelihood to Recommend Excellent value for companies wishing to host Java applications in the cloud. Utilizing hosting tools such as load balancers and network and application firewalls, Tomcat can be part of a powerful system to host web applications to thousands of users. There has been consistency in the development and support of Tomcat since its initial release in the late '90s and the best commonalities have been carried forward. If you host Java web applications, Tomcat is as good as any for an application server.
Read full review You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
Read full review Pros Fast to start up, which is useful when we need to just check that our changes are working correctly. Free, which allows us to not be involved with the finance/legal team about using it. Bundled with Spring Boot, which makes it even more convenient for our testing. Read full review Packaging of application to limit the space occupied Ease of running the application Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc Read full review Cons Using tomcat manager to troubleshoot is not very informative. Error messages are vague, you have to dig into log files for more information about the problems. Is great for simple web applications, but may not work for heavy development which may require a full J2EE stack, might like JBoss better. Security in tomcat is not straightforward, as I discovered that you have to understand how to set up realms in tomcat in order to hash passwords, which I was not overly familiar with, which is a big deal when setting up users in the tomcat-users.xml file. Read full review Docker hub image retention policy can be relaxed Docker hub policies can be more developer friendly Docker CLI help section can be improved Image and container storage (local) management can be optimized Read full review Likelihood to Renew We have a huge knowledge of the product within our company and we're satisfied with the performance.
Read full review Usability Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our
Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.
Read full review Very easy to use, great tutorials, documentation and cheat sheets out there to help you become a Docker Wiz
Read full review Reliability and Availability Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.
Read full review Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.
Read full review Performance Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.
Read full review Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.
Read full review Support Rating Well, in actuality, I have never needed support for Apache Tomcat since it is configured and ready-to-go with no configuration needed on my end.
Read full review Alternatives Considered Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it requires less memory to operate, you may realize that it is very efficient.
Read full review The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.
Read full review Scalability It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm
Read full review It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.
Read full review Return on Investment Tomcat is cheap and very quick to deploy, so it has benefited much when situation needs applications to be deployed quickly without wasting time on licensing and installations. Plenty of documentation available so no vendor training is required. Support contract is not needed as well. Read full review Reduces the number of virtual machine which impacted our quarterly billing Using docker with proxy we run multiple application on same port on same host. impact on billing is we have to provide docker training to the people who are working on it. Read full review ScreenShots