CloudFoundry vs. Google App Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CloudFoundry
Score 7.1 out of 10
N/A
CloudFoundry is a free, open source cloud computing platform supported by the non-profit CloudFoundry. It is not tied to any particular cloud service, but can be self-hosted or run on any cloud service preferred.N/A
Google App Engine
Score 8.4 out of 10
N/A
Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Pricing
CloudFoundryGoogle App Engine
Editions & Modules
No answers on this topic
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Offerings
Pricing Offerings
CloudFoundryGoogle App Engine
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CloudFoundryGoogle App Engine
Top Pros
Top Cons
Features
CloudFoundryGoogle App Engine
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
CloudFoundry
9.8
1 Ratings
18% above category average
Google App Engine
8.7
31 Ratings
6% above category average
Ease of building user interfaces10.01 Ratings9.017 Ratings
Scalability9.01 Ratings9.031 Ratings
Development environment creation10.01 Ratings8.928 Ratings
Development environment replication10.01 Ratings8.027 Ratings
Issue recovery10.01 Ratings8.925 Ratings
Upgrades and platform fixes10.01 Ratings8.028 Ratings
Platform management overhead00 Ratings8.931 Ratings
Workflow engine capability00 Ratings9.023 Ratings
Platform access control00 Ratings8.930 Ratings
Services-enabled integration00 Ratings8.027 Ratings
Issue monitoring and notification00 Ratings9.027 Ratings
Best Alternatives
CloudFoundryGoogle App Engine
Small Businesses
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
Medium-sized Companies
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
Enterprises
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CloudFoundryGoogle App Engine
Likelihood to Recommend
10.0
(1 ratings)
8.0
(35 ratings)
Likelihood to Renew
-
(0 ratings)
8.3
(8 ratings)
Usability
-
(0 ratings)
7.7
(7 ratings)
Performance
-
(0 ratings)
10.0
(1 ratings)
Support Rating
-
(0 ratings)
8.4
(12 ratings)
Implementation Rating
-
(0 ratings)
8.0
(1 ratings)
User Testimonials
CloudFoundryGoogle App Engine
Likelihood to Recommend
CloudFoundry
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.
Read full review
Google
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
Read full review
Pros
CloudFoundry
  • 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
Read full review
Google
  • Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
  • Flexible. We use Java for some services and Node.js for others.
  • Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.
Read full review
Cons
CloudFoundry
  • 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.
Read full review
Google
  • There is a slight learning curve to getting used to code on Google App Engine.
  • Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
  • Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
Read full review
Likelihood to Renew
CloudFoundry
No answers on this topic
Google
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
Read full review
Usability
CloudFoundry
No answers on this topic
Google
Google App Engine is very intuitive. It has the common programming language most would use. Google is a dependable name and I have not had issues with their servers being down....ever. You can safely use their service and store your data on their servers without worrying about downtime or loss of data.
Read full review
Support Rating
CloudFoundry
No answers on this topic
Google
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
Read full review
Alternatives Considered
CloudFoundry
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.
Read full review
Google
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
Read full review
Return on Investment
CloudFoundry
  • 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.
Read full review
Google
  • Effective employee adoption through ease of use.
  • Effective integration to other java based frameworks.
  • Time to market is very quick. Build, test, deploy and use.
  • The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
Read full review
ScreenShots