Skip to content
Branch: master
Find file History
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
dev
images
README.md Fix a typo in readme (#4191) Dec 22, 2018
about.md Fix typos in docs (#4279) Feb 13, 2019
actions-ballerina.md Add Ballerina 0.990 runtime. (#4239) Jan 26, 2019
actions-docker.md Fix typos in docs (#4279) Feb 13, 2019
actions-dotnet.md update dotnet doc to use .zip with wsk cli (#4180) Dec 15, 2018
actions-go.md
actions-java.md Reorganize actions docs (#3816) Jun 29, 2018
actions-new.md
actions-nodejs.md Updated documentation to reflect the new output from wsk activation l… Mar 19, 2019
actions-php.md Remove older runtimes. (#4254) Feb 9, 2019
actions-python.md
actions-ruby.md
actions-swift.md Fix typos in docs (#4279) Feb 13, 2019
actions.md
annotations.md
apigateway.md Fix markdown files with a typo. in the Hash license header. (#3633) May 10, 2018
catalog.md
cli.md Fix typos in docs (#4279) Feb 13, 2019
concurrency.md Update the package name and path in documents (#4166) Dec 12, 2018
conductors.md
deploy.md Fix typos in docs (#4279) Feb 13, 2019
feeds.md
logging.md
mesos.md
metrics.md
mobile_sdk.md
packages.md Fix markdown files with a typo. in the Hash license header. (#3633) May 10, 2018
parameters.md
reference.md
rest_api.md
samples.md
security.md add a doc for securing actions (#3801) Jun 25, 2018
spi.md
triggers_rules.md Updated documentation to reflect the new output from wsk activation l… Mar 19, 2019
use_cases.md Update Bluemix references in docs (#3673) May 19, 2018
webactions.md
yarn.md Adding YARNContainerFactory. This allows OpenWhisk to run actions on … Feb 23, 2019

README.md

Getting started with OpenWhisk

OpenWhisk is an Apache Incubator 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.

You can’t perform that action at this time.