Google Cloud Run vs OpenFaaS

Overview

OpenFaaS

Stacks54

Followers234

Votes17

GitHub Stars26.0K

Forks2.0K

Google Cloud Run

Stacks290

Followers243

Votes62

Google Cloud Run vs OpenFaaS: What are the differences?

Introduction:

Google Cloud Run and OpenFaaS are both serverless platforms that enable developers to deploy and run containerized applications effortlessly. However, there are key differences between the two platforms that cater to different use cases and requirements.

Deployment Flexibility: Google Cloud Run allows developers to run stateless HTTP containers, providing flexibility to deploy applications without worrying about the infrastructure. On the other hand, OpenFaaS supports event-driven, serverless functions, making it ideal for running smaller, independent functions that can be triggered by events.
Managed Service: Google Cloud Run is a fully managed service by Google Cloud Platform, taking care of scaling, networking, and security aspects. In contrast, OpenFaaS can be deployed on any infrastructure, giving users more control over the underlying environment but also requiring self-management of the platform.
Community Support: OpenFaaS has a strong community backing and an active ecosystem that contributes to the platform's growth and development. Users can benefit from a wide range of integrations, plugins, and support from the community members. Google Cloud Run, being a proprietary platform, may have limited community support compared to the open-source nature of OpenFaaS.
Pricing Model: Google Cloud Run follows a pay-as-you-go pricing model, where users are charged based on the number of requests and resources consumed. OpenFaaS, being an open-source platform, allows users to run workloads on their preferred infrastructure, potentially reducing costs for organizations that can optimize resource usage.
Security Features: Google Cloud Run offers built-in security features such as Identity-Aware Proxy (IAP), encryption at rest, and network isolation for securing applications and data. OpenFaaS, being more customizable, allows users to implement their preferred security measures, but it requires more manual configuration and management compared to the managed security features of Google Cloud Run.
Integration with Other Services: Google Cloud Run seamlessly integrates with other Google Cloud services such as Cloud Storage, Cloud Monitoring, and Cloud Logging, providing a comprehensive ecosystem for deploying and managing applications. OpenFaaS, while being platform-agnostic, may require additional configurations for integrating with external services beyond the core functionalities of the platform.

In Summary, Google Cloud Run and OpenFaaS offer distinct advantages in deployment flexibility, managed services, community support, pricing models, security features, and integration capabilities for developers and organizations seeking serverless solutions.

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 OpenFaaS, 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.3k views71.3k

Comments

Detailed Comparison

OpenFaaS	Google Cloud Run
Serverless Functions Made Simple for Docker and Kubernetes	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.
-	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
GitHub Stars 26.0K	GitHub Stars -
GitHub Forks 2.0K	GitHub Forks -
Stacks 54	Stacks 290
Followers 234	Followers 243
Votes 17	Votes 62
Pros & Cons
Pros 5 Open source 4 Ease 3 Autoscaling 2 Community 2 Documentation	Pros 11 HTTPS endpoints 10 Fully managed 10 Pay per use 7 Concurrency: multiple requests sent to each container 7 Deploy containers
Integrations
Kubernetes Docker	Google Kubernetes Engine Google Cloud Build Docker Knative

What are some alternatives to OpenFaaS, Google Cloud Run?

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

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.

Fission

Write short-lived functions in any language, and map them to HTTP requests (or other event triggers). Deploy functions instantly with one command. There are no containers to build, and no Docker registries to manage.

Related Comparisons

Google Cloud Run vs OpenFaaS: What are the differences?

Introduction:

Deployment Flexibility: Google Cloud Run allows developers to run stateless HTTP containers, providing flexibility to deploy applications without worrying about the infrastructure. On the other hand, OpenFaaS supports event-driven, serverless functions, making it ideal for running smaller, independent functions that can be triggered by events.
Managed Service: Google Cloud Run is a fully managed service by Google Cloud Platform, taking care of scaling, networking, and security aspects. In contrast, OpenFaaS can be deployed on any infrastructure, giving users more control over the underlying environment but also requiring self-management of the platform.
Community Support: OpenFaaS has a strong community backing and an active ecosystem that contributes to the platform's growth and development. Users can benefit from a wide range of integrations, plugins, and support from the community members. Google Cloud Run, being a proprietary platform, may have limited community support compared to the open-source nature of OpenFaaS.
Pricing Model: Google Cloud Run follows a pay-as-you-go pricing model, where users are charged based on the number of requests and resources consumed. OpenFaaS, being an open-source platform, allows users to run workloads on their preferred infrastructure, potentially reducing costs for organizations that can optimize resource usage.
Security Features: Google Cloud Run offers built-in security features such as Identity-Aware Proxy (IAP), encryption at rest, and network isolation for securing applications and data. OpenFaaS, being more customizable, allows users to implement their preferred security measures, but it requires more manual configuration and management compared to the managed security features of Google Cloud Run.
Integration with Other Services: Google Cloud Run seamlessly integrates with other Google Cloud services such as Cloud Storage, Cloud Monitoring, and Cloud Logging, providing a comprehensive ecosystem for deploying and managing applications. OpenFaaS, while being platform-agnostic, may require additional configurations for integrating with external services beyond the core functionalities of the platform.

Google Cloud Run vs OpenFaaS

Overview