F5 Distributed Cloud App Connect vs. IBM Cloud Pak for Applications

My advice is if your firm build multi-cloud, high availability SaaS products or you just run polyglot workloads across kubernetes and VMs, then F5 Distributed Cloud App Connect is your guy. Coming from an expert, just start with a few core services or else you will be overwhelmed.

Incentivized

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.

Incentivized

• Ease of use - standing up a new site took very little time, less then an hour.
• Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP

Incentivized

• 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.

Incentivized

• More of a unified experience as Gartner released their latest sort of sassy trends. A lot of consumers are looking at a more unified experience and that's the sort of compilation of both management and data planes into a single things like single UI, easier management experience for the corporations.

Incentivized

• User Experience and Learning Curve
• Integration with Third-party Tools
• Pricing and Licensing Model

Incentivized

The management console is generally fast. I constantly have changes reflect so quickly across environments. When pushing updates via GitOps or API , F5 Distributed Cloud App Connect applies changes near instantly.

Incentivized

It's pretty clear that these two are fine within a single ecosystem but fall short when the architecture spans more than one cloud vendor.

Incentivized

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.

Incentivized

• It has cut down engineering time for fragile edge failovers by over 40 percent - on high availability setups
• An overall lowered cost of ownership for cloud networking, i estimate it to be around 20%
• Reduced deployment complexity by half

Incentivized

• 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.

Incentivized