Need advice about which tool to choose?Ask the StackShare community!

Apache OpenWhisk

59
148
+ 1
7
Google Cloud Run

262
229
+ 1
62
Add tool

Apache OpenWhisk vs Google Cloud Run: What are the differences?

Developers describe Apache OpenWhisk as "A serverless, open-source cloud platform". Apache OpenWhisk (incubating) is a serverless, open source cloud platform that executes functions in response to events at any scale. On the other hand, Google Cloud Run is detailed 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.

Apache OpenWhisk and Google Cloud Run can be primarily classified as "Serverless / Task Processing" tools.

Some of the features offered by Apache OpenWhisk are:

  • Fine-grained resource consumption
  • Use any language, any service
  • Plug your service into Apache OpenWhisk

On the other hand, Google Cloud Run provides the following key features:

  • Simple developer experience
  • Fast autoscaling
  • Managed

Apache OpenWhisk is an open source tool with 4.1K GitHub stars and 791 GitHub forks. Here's a link to Apache OpenWhisk's open source repository on GitHub.

Decisions about Apache OpenWhisk and Google Cloud Run
Clifford Crerar
Software Engineer at Bidvest Advisory Services · | 9 upvotes · 66.4K views

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.
See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Apache OpenWhisk
Pros of Google Cloud Run
  • 4
    You are not tied to a provider. IBM available however
  • 3
    Still exploring... its just intresting
  • 11
    HTTPS endpoints
  • 10
    Fully managed
  • 10
    Pay per use
  • 7
    Concurrency: multiple requests sent to each container
  • 7
    Deploy containers
  • 7
    Serverless
  • 6
    Custom domains with auto SSL
  • 4
    "Invoke IAM permission" to manage authentication
  • 0
    Cons

Sign up to add or upvote prosMake informed product decisions

What is 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.

What is Google Cloud Run?

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Apache OpenWhisk?
What companies use Google Cloud Run?
See which teams inside your own company are using Apache OpenWhisk or Google Cloud Run.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Apache OpenWhisk?
What tools integrate with Google Cloud Run?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Apache OpenWhisk and 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.
Kubeless
Kubeless is a Kubernetes native serverless Framework. Kubeless supports both HTTP and event based functions triggers. It has a serverless plugin, a graphical user interface and multiple runtimes, including Python and Node.js.
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.
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.
Apex
Apex is a small tool for deploying and managing AWS Lambda functions. With shims for languages not yet supported by Lambda, you can use Golang out of the box.
See all alternatives