Amazon EC2 Auto Scaling helps users maintain application availability and allows users to automatically add or remove EC2 instances according to definable conditions.
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.
If you need to establish a system right away, in the past it took weeks or months to request a quote from the vendor and receive the equipment. Now, with Amazon EC2 in less than tens of minutes or hours, you can create a test environment and test it without any inconvenience.
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.
Usability is good since we already know how AWS works. For those that are new it might be a little bit confusing at the beginning but they are improving it at a fast pace. Even though AWS keeps changing the user interface constantly, it is still powerful, understandable and easy to use. For technical people, they still offer the CLI.
The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems. Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.
The main reason is our total infra is created on AWS and we tend to use the natural service by AWS rather than third party tools, which has more advantages when the auto scaling interacts with other AWS services and its way easy to configure when we compare it with counter parts like Autoscale from Microsoft Azure.
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.
We will devote more time to development than server administration, but we will require additional time if you migrate from another ecosystem.
Fault detection and reporting are automated in the old server, and bandwidth is fixed per month, but everything is manageable automatically. We only pay for the resources we use.
After some months, we met our return on investment (ROI).
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.
