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.
Less appropriate: - Not best bet for startup’s as their budget is always tight - Not good for those companies where the engineers are not highly skilled otherwise the use Irules and security policies will not be utilised in optimal manner as it requires more cpu resources to work especially irules - For companies fully on cloud doesn’t best fit as I already highlighted cloud require more improvements when it comes to seamless performance Best Suited -Large enterprise companies where budget is not an issue - Companies whose traffic Rate Per Second is very high as it can handle huge RPS without latency - Companies whose business is surely depends on their availability
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.
I'd like to see better reporting capabilities on the decision-making process for DNS resolutions. Currently there are plenty of log messages for that, but I'd like to see tighter integration into the GUI.
It could be an improvement to better discriminate features intended for AA vs LDNS functionality within the GUI.
We use this heavily and it is one of the best products out there for this type of use case. We already have LTMs and to leverage GTM on top of that is just a piece of cake. Everything is so well integrated its amazing
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.
Most important usability of F5 BIG-IP DNS is it’s stability which other vendors lack -As mentioned earlier as well, it’s scalability is humongous as it can honour millions of request per second without latency - irules feature makes it top and worthy to fight with top contenders like cloudflare and Cisco - Moreover it’s stable even when the Rate Per second is high and at the same time, DDos occurs - Interface is user friendly for simple tasks but requires more manual work - TAC should provide more assistance when it comes to normal support as well but they do offer professional support license for tasks which other vendor assist on normal license as well
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.
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.
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.
As I mentioned, the GSLB capability, being able to do intelligent DNS by having access to monitor specific endpoints associated to my current BIG-IP infrastructure, I believe that brings a huge value, then combine fast responses and security.
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.
Saved almost 1.2 million USD for one of critical activities as downtime could have posed this but due to failover based on health checks saved these bucks
Business impact which can be caused due to DDos attacks avoided
High cost licensing as mentioned earlier as well
Analytical limitations as F5 has also mentioned multiple it’s not an analytical tool
