Item: IBM Cloud Foundry
Rating: 5
Author: Sashikanth Vema

Use Cases and Deployment Scope

IBM Cloud Foundry is used on IBM Cloud for applications across the organization.

Pros and Cons

Easy to use
Bind services (catalog)

Not easily extendable
Lacks in observability

Return on Investment

No environment set up, easier for teams to move to cloud than request for environments.
Catalog services makes it easier as we don't need to provision any services.
Issues with patching

IBM Cloud Foundry Fault Tolerance

We have a minimum number of instances which is 3. If any app instances go down, automatically a new instance is spun up. However, it's difficult to get thread dumps etc., for analysis of the failed instance.

IBM Cloud Foundry Language Support

We use Java and NodeJS primarily; it's easier to use those buildpacks.

Other Software Used

Dynatrace Application Monitoring

Likelihood to Recommend

Easier to deploy microservice applications. Buildpacks abstract out quite a bit of configuration. Polyglot development. Abstracts out the containers that are built for the runtimes. Difficult for AI/ML type of workloads. Lacks in observability, trying to work out a custom solution for observability. Still evolving for K8s and not sure how to handle K8 workloads.

CF is easy to adopt to, but difficult to extend

Overall Satisfaction with IBM Cloud Foundry