CloudFoundry vs. Oracle Cloud Platform

It's well suited if:

• The organization has large number of applications that needs to be deployed frequently.
• The organization is tied to the DevOps mindset.
• The organization has programs in different languages.
• The applications does not need EJB's support that servers like web logic provide.

It's less suited if:

• The applications needs security configuration within the same CloudFoundry instance.
• The organization, for whatever reason does not want developers to manage the instances.

Incentivized

We had been slowly implementing Oracle products to replace several existing systems and so we needed a platform that would work to integrate across all of these solutions. Our company is fairly large and we work with a variety of clients and vendors as well. We needed an easier way for everyone to access information and discuss what data and future integration were most appropriate.

Incentivized

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Incentivized

• Oracle Cloud Platform can provide consistent latency guarantees in multiple geographics.
• It works well with Oracle Database that is being used as the primary database without the need for custom configuration.
• Oracle Cloud Platform has reasonable customization options to fine-tune it for workloads that require very low latency for events/transactions.

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

Incentivized

• Going with any Oracle Cloud Platform Solution for BI Implementation, I would prefer a strong/powerful Oracle tool to push data in Oracle Cloud Datawarehouse.
• There are chances of overage charges on using the Oracle Cloud Platform, if you choose to implement any services with non-allocated core CPU. So expect to give some alert before even allowing to implement any service with not allocated core CPU or remove the displaying of non-allocated CPUs for users.
• It can allow options where Oracle Cloud storage container username password as never expired.

Incentivized

While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.

Incentivized

If you already have considerable Oracle licenses, then Oracle Cloud Platform is the best option. If most of your applications and needs are Windows-based, then Microsoft Azure is the best choice. Google GCP is on par with Oracle Cloud Platform in various features, including global reach. Cisco Hybrid Cloud Platform is an excellent choice if you have some interesting network requirements for the application to be deployed.

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

Incentivized

• I only used the trial version, but I liked the rich UI experience. It was easy to understand. I liked the fact that there are a lot of apps in the app store. A lot of brands use Oracle which leads to trust. It's also scalable.
• As a consultant, this is something I can recommend to my customers over Amazon AWS Cloud because it has the built-in security that you don't have to buy separately.
• Easy to integrate. My clients are looking for a one-stop ecosystem that can be used for everything including HR, Security, Analytics, Dashboards, and user experience. This saves me time as a consultant as well.

Incentivized