Google App Engine vs Google Cloud Run

Overview

Google App Engine

Stacks10.5K

Followers8.1K

Votes611

Google Cloud Run

Stacks292

Followers243

Votes62

Google App Engine vs Google Cloud Run: What are the differences?

Deployment Flexibility: Google App Engine provides a Platform as a Service (PaaS) environment, allowing users to deploy applications without worrying about infrastructure management. On the other hand, Google Cloud Run offers a more flexible approach by enabling users to run stateless containers on a fully managed environment or even on their own Kubernetes cluster, providing better control over deployment configurations.
Scalability: While both platforms support auto-scaling to handle varying workloads, Google App Engine scales automatically based on incoming traffic, making it more suitable for applications with unpredictable usage patterns. In comparison, Google Cloud Run can be configured to scale based on more specific metrics like CPU utilization, offering finer control over resource allocation.
Pricing Model: Google App Engine follows a pricing model based on instance hours and resources consumed, which may result in more predictable costs for long-running applications. Conversely, Google Cloud Run charges users based on the number of requests and vCPU utilization, making it more cost-effective for applications with sporadic traffic.
Portability: Google App Engine requires developers to adhere to certain constraints and dependencies specific to the platform, potentially limiting the portability of applications to other environments. On the contrary, Google Cloud Run allows users to encapsulate their applications in containers, promoting portability across various cloud providers and on-premises environments.
Execution Environment: Google App Engine abstracts the underlying infrastructure and provides a ready-to-use runtime environment for deploying applications, simplifying the development process. In contrast, Google Cloud Run grants users more control over the container execution environment, allowing them to customize aspects like environment variables and entry points for greater flexibility.
Use Cases: Google App Engine is well-suited for developing and deploying simple web applications and APIs quickly, thanks to its streamlined deployment process and auto-scaling capabilities. On the other hand, Google Cloud Run caters to users seeking a serverless container platform for running microservices or complex workloads that require more control over resources and scalability.

In Summary, Google App Engine and Google Cloud Run differ in deployment flexibility, scalability, pricing model, portability, execution environment, and use cases, catering to distinct application development requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Google App Engine, Google Cloud Run

Clifford

Software Engineer at Bidvest Advisory Services

Mar 28, 2020

Decided

Run cloud service containers instead of cloud-native services

Running containers means that your microservices are not "cooked" into a cloud provider's architecture.
Moving from one cloud to the next means that you simply spin up new instances of your containers in the new cloud using that cloud's container service.
Start redirecting your traffic to the new resources.
Turn off the containers in the cloud you migrated from.

71.4k views71.4k

Comments

Detailed Comparison

Google App Engine	Google Cloud Run
Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.	A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.
Zero to sixty: Scale your app automatically without worrying about managing machines.;Supercharged APIs: Supercharge your app with services such as Task Queue, XMPP, and Cloud SQL, all powered by the same infrastructure that powers the Google services you use every day.;You're in control: Manage your application with a simple, web-based dashboard allowing you to customize your app's performance.	Simple developer experience; Fast autoscaling; Managed; Any language, any library, any binary; Leverage container workflows and standards; Redundancy; Integrated logging and monitoring; Built on Knative; Custom domains
Statistics
Stacks 10.5K	Stacks 292
Followers 8.1K	Followers 243
Votes 611	Votes 62
Pros & Cons
Pros 145 Easy to deploy 106 Auto scaling 80 Good free plan 62 Easy management 56 Scalability	Pros 11 HTTPS endpoints 10 Fully managed 10 Pay per use 7 Concurrency: multiple requests sent to each container 7 Deploy containers
Integrations
Red Hat Codeready Workspaces Twilio Twilio SendGrid	Google Kubernetes Engine Google Cloud Build Docker Knative

What are some alternatives to Google App Engine, Google Cloud Run?

Heroku

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Red Hat OpenShift

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

AWS Lambda

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

AWS Elastic Beanstalk

Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

Render

Render is a unified platform to build and run all your apps and websites with free SSL, a global CDN, private networks and auto deploys from Git.

Hasura

An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.

Cloud 66

Cloud 66 gives you everything you need to build, deploy and maintain your applications on any cloud, without the headache of dealing with "server stuff". Frameworks: Ruby on Rails, Node.js, Jamstack, Laravel, GoLang, and more.

Jelastic

Jelastic is a Multi-Cloud DevOps PaaS for ISVs, telcos, service providers and enterprises needing to speed up development, reduce cost of IT infrastructure, improve uptime and security.

Dokku

It is an extensible, open source Platform as a Service that runs on a single server of your choice. It helps you build and manage the lifecycle of applications from building to scaling.

Related Comparisons

Google App Engine vs Google Cloud Run: What are the differences?

Deployment Flexibility: Google App Engine provides a Platform as a Service (PaaS) environment, allowing users to deploy applications without worrying about infrastructure management. On the other hand, Google Cloud Run offers a more flexible approach by enabling users to run stateless containers on a fully managed environment or even on their own Kubernetes cluster, providing better control over deployment configurations.
Scalability: While both platforms support auto-scaling to handle varying workloads, Google App Engine scales automatically based on incoming traffic, making it more suitable for applications with unpredictable usage patterns. In comparison, Google Cloud Run can be configured to scale based on more specific metrics like CPU utilization, offering finer control over resource allocation.
Pricing Model: Google App Engine follows a pricing model based on instance hours and resources consumed, which may result in more predictable costs for long-running applications. Conversely, Google Cloud Run charges users based on the number of requests and vCPU utilization, making it more cost-effective for applications with sporadic traffic.
Portability: Google App Engine requires developers to adhere to certain constraints and dependencies specific to the platform, potentially limiting the portability of applications to other environments. On the contrary, Google Cloud Run allows users to encapsulate their applications in containers, promoting portability across various cloud providers and on-premises environments.
Execution Environment: Google App Engine abstracts the underlying infrastructure and provides a ready-to-use runtime environment for deploying applications, simplifying the development process. In contrast, Google Cloud Run grants users more control over the container execution environment, allowing them to customize aspects like environment variables and entry points for greater flexibility.
Use Cases: Google App Engine is well-suited for developing and deploying simple web applications and APIs quickly, thanks to its streamlined deployment process and auto-scaling capabilities. On the other hand, Google Cloud Run caters to users seeking a serverless container platform for running microservices or complex workloads that require more control over resources and scalability.

Google App Engine vs Google Cloud Run

Overview