CloudFoundry vs. Google 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

When most of our stuff is in Google Cloud Platform, it works great to integrate and cross/share data that is all in Google Cloud Platform or BigQuery. It has simplified things from a permissions perspective as well. I'd say it is less appropriate when trying to test something quickly locally, or when half your stuff is in AWS or another provider.

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

• Easy to set up
• Affordable use of the tool
• Easy to access billing
• Reliable service

Incentivized

• 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

• The UI is so confusing. The console is good, but it is like a maze. There are too many menus and settings, and things do not work as expected. It takes time to get friendly, and it is not friendly for new users.
• Support experience: Sometimes, you get a great engineer, but other times, it's very difficult to talk with them as they are unable to respond as expected and solve issues late.
• Region and zone are issues, as not all services are available in all regions, which is lacking when deploying something in the same region or zone.

Incentivized

The Google Cloud Platform console is pretty slick for BigQuery especially. I have liked the visibility I get from using that and the way to integrate and see what's in our data lake. The logging console for tracking GKE jobs isn't quite as great, which is why it doesn't get a full 10.

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

Google Cloud Platform is release later than Amazon web service, I think that why Google Cloud Platform can learned and optimized the Dashboard and some features that make it easy to use and can be cheaper than amazon web service.

• 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

• It allows us to focus our efforts on other, more important items at hand
• It gives us an affordable option letting me know it's available to all users, not just the largest scale ones out there
• The customer service is always helpful and reliable, along with the service itself which lets me focus on my work instead of worrying about the service.

Incentivized