Tomcat is an open-source web server supported by Apache.
N/A
IBM Cloud Pak for Applications
Score 7.3 out of 10
N/A
IBM Cloud Pak® for Applications (CP4Apps) is an end-to-end hybrid cloud application platform, providing flexibility for deployments, building new cloud-native applications, refactoring and re-platforming existing applications. Designed to leverage a collection of application runtimes, modernization tools and a Kubernetes container platform to adapt to their landscape needs.
N/A
Pricing
Apache Tomcat
IBM Cloud Pak for Applications
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Tomcat
IBM Cloud Pak for Applications
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Tomcat
IBM Cloud Pak for Applications
Features
Apache Tomcat
IBM Cloud Pak for Applications
Application Servers
Comparison of Application Servers features of Product A and Product B
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.
Well suited for customers who are looking for cloud-adoption, and finally to meet the challenges of business innovation for the competitive advantage through DevOps.
Provides a fantastic range of Application runtimes allowing the most suitable runtime to be selected for the app being implemented.
After using Transformation Advisor for quite a while, it is an indispensable tool to help modernize, specifically from WebSphere and Tomcat, towards the lightweight, fast and efficient Liberty runtime.
The simplicity of the licensing by wrapping many products into a single offering with a different VPC weighting.
Allows us to modernize our runtime from WebSphere Application Server (or ND) to WebSphere Liberty core without sacrificing our WAS licenses.
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.
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.
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.
Our customer mission-critical core banking applications like Temenos T24 run on best of the breed IBM WebSphere Application Server which is java based-application server. IBM has kept up the promise of providing support, fixpack, and any update. As far as I know, at least by 2030, IBM is committed to continue with WHE which gives customers confidence in their current investments.
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.
We have been able to migrate apps away from the expensive WAS-ND to the more cost-effective WAS-base without throwing away our WAS-ND licenses. With a 1:4 ratio of WAS-ND to WAS-base we've been able to we've been able to save in excess of 75% on licensing charges for these apps.
By having a license model based on VPC ratios (1:4:8 - WAS-ND:WAS-base:Liberty core) we've been able to move away from using license pooling resulting in over-allocating (i.e. wasting) CPU cores for each license pool, to using consolidated license pools hosting a combination of WAS-ND, WAS-base and Liberty-core. This has allowed us to reduce our licensing costs accordingly.
