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.
I think it's best suited for all the monolithic application where you just need a VM and you on top of that VM you need to install a compatible product. So it's best suited for those. Where's not suited. As I said, maybe I've seen in my organization mostly our internal application teams, they go for a different operating system for appliances or network maybe it might be due to the product compatibility, not with Red Hat Enterprise Linux (RHEL), but that's something maybe you should have a look or probably it's not a improvement anywhere.
I really love that Red Hat Enterprise Linux (RHEL) is reliable, that it always seems to work well.
It's very secure.
I really appreciate that Red Hat keeps everything up to date and they are on top of security, mobilities, et cetera. I'd say those are my favorite things.
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.
Well, one of the things, this ties right back to my previous answer from what it sounds like, the cloud platform for Insights doesn't currently have an easy way to generate CVE compliance reports, or do scans for where you have remediations required, but it does not currently produce those reports in a way that I could just hand off to our security team and be like, here's our compliance, here's where all the things are specifically because Red Hat does backporting of patches and a lot of security tools don't know how to handle that and think that we're vulnerable when we're not. So from everything I've heard, it's possible. That's why I'm excited for it. But it's not easily pushed button generated report yet. So we're working with them to get that in there.
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.
RHEL has most of the features that are required by an ERP solution. If you need any additional packages, RHEL has a great repository and a very easy package installation/upgrade process.
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.
Red Hat support has really come a long way in the last 10 years, The general support is great, and the specialized product support teams are extremely knowledgeable about their specific products. Response time is good and you never need to escalate.
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.
The biggest thing about RHEL that makes it stand out for enterprise users is the support that we get from the vendor. Whereas with the other ones, you're basically left on your own. There's no official repo, there's no satellite for patching. You're very left on your own with the community.
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.
It's only been positive and like I said before, it's been positive because it removed tedious tasks and I think that's probably what it's designed to help do from what I can tell is just to get rid of the mundane tasks of a systems administrator. The things that you just don't want to waste time doing so you can actually use your brain for something useful.