Skip to content

Files

Latest commit

a4508ba · Sep 24, 2024

History

History

docs

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Oct 7, 2021
Nov 1, 2022
Jan 10, 2020
Aug 14, 2019
Aug 14, 2019
Aug 18, 2022
Aug 18, 2022
Feb 18, 2023
Aug 18, 2022
Sep 24, 2024
Jul 13, 2023
Aug 18, 2022
Aug 18, 2022
Aug 18, 2022
Aug 18, 2022
Aug 18, 2022
Sep 20, 2019
Sep 24, 2024
Jun 3, 2020
Aug 14, 2019
Aug 14, 2019
Nov 8, 2019
Mar 19, 2019
Jul 24, 2022
Mar 6, 2024
May 10, 2018
May 4, 2023
May 10, 2018
Feb 22, 2020
May 10, 2018
Feb 13, 2019
May 4, 2023
Jan 25, 2023
Aug 14, 2019
Jun 25, 2018
Sep 24, 2024
Feb 13, 2019
Jul 22, 2022
Mar 19, 2019
Sep 24, 2024
Jan 25, 2023
Aug 27, 2019
Feb 23, 2019

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.