Google Cloud Run vs faasd

Overview

Google Cloud Run

Stacks290

Followers243

Votes62

faasd

Stacks0

Followers6

Votes0

GitHub Stars3.2K

Forks230

Google Cloud Run vs faasd: What are the differences?

Developers describe Google Cloud Run as "Run stateless HTTP containers on a fully managed environment or in your own GKE cluster". 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. On the other hand, faasd is detailed as "Lightweight OSS Serverless". It is the same OpenFaaS experience and ecosystem, but without Kubernetes. Functions and microservices can be deployed anywhere with reduced overheads whilst retaining the portability of containers and cloud-native tooling such as containerd and CNI.

Google Cloud Run and faasd can be categorized as "Serverless / Task Processing" tools.

Some of the features offered by Google Cloud Run are:

Simple developer experience
Fast autoscaling
Managed

On the other hand, faasd provides the following key features:

A single Golang binary
Can be set-up and left alone to run your applications
Multi-arch, so works on Intel x86_64 and ARM out the box

🔥 Trending in Serverless on StackShare

AWS Lambda Serverless

Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB

Try it View Docs Alternatives

Try

223

18.8k

Advice on Google Cloud Run, faasd

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

Google Cloud Run	faasd
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.	It is the same OpenFaaS experience and ecosystem, but without Kubernetes. Functions and microservices can be deployed anywhere with reduced overheads whilst retaining the portability of containers and cloud-native tooling such as containerd and CNI.
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	A single Golang binary; Can be set-up and left alone to run your applications; Multi-arch, so works on Intel x86_64 and ARM out the box; Uses the same core components and ecosystem of OpenFaaS
Statistics
GitHub Stars -	GitHub Stars 3.2K
GitHub Forks -	GitHub Forks 230
Stacks 290	Stacks 0
Followers 243	Followers 6
Votes 62	Votes 0
Pros & Cons
Pros 11 HTTPS endpoints 10 Pay per use 10 Fully managed 7 Concurrency: multiple requests sent to each container 7 Serverless	No community feedback yet
Integrations
Google Kubernetes Engine Google Cloud Build Docker Knative	DigitalOcean Linux Raspberry Pi macOS Windows

What are some alternatives to Google Cloud Run, faasd?

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.

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.

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

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

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

Serverless Functions Made Simple for Docker and Kubernetes

Nuclio

nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.

Apache OpenWhisk

OpenWhisk is an open source serverless platform. It is enterprise grade and accessible to all developers thanks to its superior programming model and tooling. It powers IBM Cloud Functions, Adobe I/O Runtime, Naver, Nimbella among others.

Cloud Functions for Firebase

Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.

AWS Batch

It enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. It dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted.