Skip to content

Latest commit

 

History

History

docs

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
dev
dev
 
 
images
images
 
 
README.md
README.md
 
 
about.md
about.md
 
 
actions-actionloop.md
actions-actionloop.md
 
 
actions-docker.md
actions-docker.md
 
 
actions-dotnet.md
actions-dotnet.md
 
 
actions-go.md
actions-go.md
 
 
actions-java.md
actions-java.md
 
 
actions-new.md
actions-new.md
 
 
actions-nodejs.md
actions-nodejs.md
 
 
actions-php.md
actions-php.md
 
 
actions-python.md
actions-python.md
 
 
actions-ruby.md
actions-ruby.md
 
 
actions-rust.md
actions-rust.md
 
 
actions-swift.md
actions-swift.md
 
 
actions-update.md
actions-update.md
 
 
actions.md
actions.md
 
 
annotations.md
annotations.md
 
 
apigateway.md
apigateway.md
 
 
catalog.md
catalog.md
 
 
cli.md
cli.md
 
 
conductors.md
conductors.md
 
 
dedicated-invokers.md
dedicated-invokers.md
 
 
deploy.md
deploy.md
 
 
feeds.md
feeds.md
 
 
intra-concurrency.md
intra-concurrency.md
 
 
logging.md
logging.md
 
 
metrics.md
metrics.md
 
 
packages.md
packages.md
 
 
parameters.md
parameters.md
 
 
reference.md
reference.md
 
 
rest_api.md
rest_api.md
 
 
samples.md
samples.md
 
 
security.md
security.md
 
 
single_entrypoint_proxy_contract.md
single_entrypoint_proxy_contract.md
 
 
spi.md
spi.md
 
 
tag-based-scheduling.md
tag-based-scheduling.md
 
 
triggers_rules.md
triggers_rules.md
 
 
use_cases.md
use_cases.md
 
 
warmed-containers.md
warmed-containers.md
 
 
webactions.md
webactions.md
 
 
yarn.md
yarn.md
 
 

README.md

Getting started with OpenWhisk

OpenWhisk is an Apache Software Foundation (ASF) project. It is an open source implementation of a distributed, event-driven compute service. You can run it on your own hardware on-prem, or in the cloud. When running in the cloud you could use a Platform as a Service (PaaS) version of the OpenWhisk provided by IBM Cloud Functions, or you can provision it yourself into Infrastructure as a Service (IaaS) clouds, such as IBM Cloud, Amazon EC2, Microsoft Azure, Google GCP, etc.

OpenWhisk runs application logic in response to events or direct invocations from web or mobile apps over HTTP. Events can be provided from IBM Cloud services like Cloudant and from external sources. Developers can focus on writing application logic, and creating actions that are executed on demand. The benefits of this new paradigm are that you do not explicitly provision servers and worry about auto-scaling, or worry about high availability, updates, maintenance and pay for hours of processor time when your server is running but not serving requests. Your code executes whenever there is an HTTP call, database state change, or other type of event that triggers the execution of your code. You get billed by millisecond of execution time (rounded up to the nearest 100ms in case of OpenWhisk) or on some platforms per request (not supported on OpenWhisk yet), not per hour of JVM regardless whether that VM was doing useful work or not.

This programming model is a perfect match for microservices, mobile, IoT and many other apps – you get inherent auto-scaling and load balancing out of the box without having to manually configure clusters, load balancers, http plugins, etc. All you need to do is to provide the code you want to execute and give it to your cloud vendor. The rest is “magic”. A good introduction into the serverless programming model is available on Martin Fowler's blog.

Overview

Implementation guide

Programming model

Official OpenWhisk project website http://OpenWhisk.org.