StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Container Registry
  4. Containers As A Service
  5. AWS Fargate vs Google Cloud Run

AWS Fargate vs Google Cloud Run

OverviewDecisionsComparisonAlternatives

Overview

AWS Fargate
AWS Fargate
Stacks650
Followers413
Votes0
Google Cloud Run
Google Cloud Run
Stacks291
Followers243
Votes62

AWS Fargate vs Google Cloud Run: What are the differences?

Key Differences between AWS Fargate and Google Cloud Run

AWS Fargate and Google Cloud Run are both serverless compute services that enable users to deploy containerized applications on a cloud platform. However, there are several key differences between the two platforms.

  1. Billing Model: AWS Fargate follows a pay-per-use billing model, where users are billed based on the amount of CPU and memory resources consumed by their containers. In contrast, Google Cloud Run charges customers based on the number of requests made to their applications, as well as the duration of those requests.

  2. Containerization Technology: AWS Fargate uses Docker as its containerization technology, allowing users to build, deploy, and manage containers using the Docker ecosystem. On the other hand, Google Cloud Run leverages Knative, an open-source platform for deploying and managing serverless workloads, offering users a more flexible and extensible containerization technology.

  3. Service Scaling: AWS Fargate provides auto-scaling capabilities, allowing users to automatically adjust the number of containers based on the workload demand. This ensures optimal performance and cost-efficiency. Google Cloud Run, on the other hand, offers built-in auto-scaling for requests, scaling the number of instances up or down based on the number of incoming requests.

  4. Service Integration: AWS Fargate seamlessly integrates with other AWS services such as Elastic Load Balancing, Amazon VPC, and AWS CloudFormation, providing users with a comprehensive ecosystem of cloud services. In contrast, Google Cloud Run integrates with other Google Cloud services like Cloud Pub/Sub and Cloud Build, enabling users to take advantage of Google's ecosystem.

  5. Platform Maturity: AWS Fargate has been available since 2017 and has a more mature ecosystem with a wide range of features and documentation. Google Cloud Run, launched in 2019, is a newer platform and may have a smaller community and fewer resources available.

  6. Deployment Options: AWS Fargate supports deploying containers as standalone tasks within an Amazon ECS or EKS cluster, providing users with more options for deployment. On the other hand, Google Cloud Run only supports deploying applications as stateless HTTP containers, limiting the types of applications that can be deployed.

In summary, AWS Fargate and Google Cloud Run differ in their billing models, containerization technologies, scaling capabilities, service integrations, platform maturity, and deployment options. Users should consider these differences in order to determine which platform best suits their specific needs and 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)
or
Manual

Advice on AWS Fargate, Google Cloud Run

Clifford
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.3k views71.3k
Comments

Detailed Comparison

AWS Fargate
AWS Fargate
Google Cloud Run
Google Cloud Run

AWS Fargate is a technology for Amazon ECS and EKS* that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure, and scale clusters of virtual machines to run containers.

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.

No clusters to manage; seamless scaling; Integrated with Amazon ECS and EKS
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
650
Stacks
291
Followers
413
Followers
243
Votes
0
Votes
62
Pros & Cons
Cons
  • 2
    Expensive
Pros
  • 11
    HTTPS endpoints
  • 10
    Pay per use
  • 10
    Fully managed
  • 7
    Concurrency: multiple requests sent to each container
  • 7
    Deploy containers
Integrations
Docker
Docker
Amazon EC2 Container Service
Amazon EC2 Container Service
Amazon CloudWatch
Amazon CloudWatch
AWS IAM
AWS IAM
Amazon VPC
Amazon VPC
Google Kubernetes Engine
Google Kubernetes Engine
Google Cloud Build
Google Cloud Build
Docker
Docker
Knative
Knative

What are some alternatives to AWS Fargate, Google Cloud Run?

AWS Lambda

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.

Amazon EC2 Container Service

Amazon EC2 Container Service

Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles.

Google Kubernetes Engine

Google Kubernetes Engine

Container Engine takes care of provisioning and maintaining the underlying virtual machine cluster, scaling your application, and operational logistics like logging, monitoring, and health management.

Azure Functions

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Containerum

Containerum

Containerum is built to aid cluster management, teamwork and resource allocation. Containerum runs on top of any Kubernetes cluster and provides a friendly Web UI for cluster management.

Serverless

Serverless

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.

Google Cloud Functions

Google Cloud Functions

Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

Knative

Knative

Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center

OpenFaaS

OpenFaaS

Serverless Functions Made Simple for Docker and Kubernetes

Azure Container Service

Azure Container Service

Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. You get an open solution that offers portability for both your containers and your application configuration. You select the size, the number of hosts, and choice of orchestrator tools, and Container Service handles everything else.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot