Tomcat is more than enough to deploy most of the mid-end web applications without any problem but for the high-end applications which require high scalability and high availability, which might need some tune-ups with the support of expertise in this regard. Otherwise, you may realize numerous performance issues, memory leaks, server crashes etc.
Red Hat Enterprise Linux (RHEL) is well suited for cloud environments, fast deployments and to run non-intensive apps/tools (with low memory and low cpu consumption).Red Hat Enterprise Linux (RHEL) might not be suited for really huge databases and intensive CPU processing.
Virtualization, like the operating system level task. I see this product is very good and it blends very well with the middleware components like all the JBoss and other things. And other than that, either you install it or a virtual machine or physical servers, it works seamlessly anywhere. And if you want to go further, like Red Hat OpenShift or those things also work very nice with it.
tomcat is just part of the J2EE specification implementation, majorly focusing on the servlet (front-end) part. If you requires the full J2ee stack, like EJB support, you need consider other containers like Weblogic
tomcat's cluster level support is very limited
tomcat's admin/configuration is not so intuitive, and default logging needs a lot of improvement
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.
The Red Hat Enterprise Linux (RHEL) distro is the simplest enterprise version of Red Hat that is enterprise supported and when you deploy as many VMs as we do, it is vital to have that enterprise support. On top of the enterprise support, having access to a commercially supported backbone for updates and upgrades is a huge plus.
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.
Commercial application servers are available that support enterprise application needs, but many times this is overkill for most web applications running in the cloud, particularly for independent software vendors. The capabilities and management tools provided with these applications are superior to Tomcat, but most times unnecessary for the vast majority of web applications developed in Java.
It's superior. I mean they're all Linux so it's all that code, but I find that the intangibles that you get with Red Hat, meaning the enterprise support, the lifecycle, that's what clearly makes it better than the rest of them.
It has simplified administration efforts, thus saving much time to focus on other projects and issues.
It saves us in costs, as there are no licensing requirements.
It gives us the ability to manage all of our java applets in one place, so as to be able to host both development and production systems on one server.
