Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Apisix | 12,983 | 12 hours ago | 497 | apache-2.0 | Lua | |||||
The Cloud-Native API Gateway | ||||||||||
Openwhisk | 6,233 | 19 days ago | 389 | apache-2.0 | Scala | |||||
Apache OpenWhisk is an open source serverless cloud platform | ||||||||||
Camel K | 803 | 11 | a day ago | 46 | May 29, 2023 | 162 | apache-2.0 | Go | ||
Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers | ||||||||||
Apisix Docker | 607 | 11 days ago | 5 | apache-2.0 | Dockerfile | |||||
the docker for Apache APISIX | ||||||||||
Openwhisk Deploy Kube | 285 | a month ago | 50 | apache-2.0 | Shell | |||||
The Apache OpenWhisk Kubernetes Deployment repository supports deploying the Apache OpenWhisk system on Kubernetes and OpenShift clusters. | ||||||||||
Ayame | 284 | a month ago | apache-2.0 | Go | ||||||
WebRTC Signaling Server Ayame | ||||||||||
Openwhisk Devtools | 168 | a year ago | 22 | apache-2.0 | JavaScript | |||||
Development tools for building and deploying Apache OpenWhisk | ||||||||||
Openwhisk Cli | 99 | 7 months ago | 13 | March 26, 2021 | 110 | apache-2.0 | Go | |||
Apache OpenWhisk Command Line Interface (CLI) | ||||||||||
Openwhisk Client Js | 82 | 539 | 54 | 6 days ago | 57 | August 22, 2022 | 17 | apache-2.0 | JavaScript | |
JavaScript client library for the Apache OpenWhisk platform | ||||||||||
Openwhisk Wskdeploy | 74 | 9 months ago | 8 | April 07, 2021 | 178 | apache-2.0 | Go | |||
Apache OpenWhisk utility for deploying and managing OpenWhisk projects and packages |
OpenWhisk is a serverless functions platform for building cloud applications. OpenWhisk offers a rich programming model for creating serverless APIs from functions, composing functions into serverless workflows, and connecting events to functions using rules and triggers. Learn more at http://openwhisk.apache.org.
The easiest way to start using OpenWhisk is to install the "Standalone" OpenWhisk stack. This is a full-featured OpenWhisk stack running as a Java process for convenience. Serverless functions run within Docker containers. You will need Docker, Java and Node.js available on your machine.
To get started:
git clone https://github.com/apache/openwhisk.git
cd openwhisk
./gradlew core:standalone:bootRun
When the OpenWhisk stack is up, it will open your browser to a functions Playground, typically served from http://localhost:3232. The Playground allows you create and run functions directly from your browser.
To make use of all OpenWhisk features, you will need the OpenWhisk command line tool called
wsk
which you can download from https://s.apache.org/openwhisk-cli-download.
Please refer to the CLI configuration for additional details. Typically you
configure the CLI for Standalone OpenWhisk as follows:
wsk property set \
--apihost 'http://localhost:3233' \
--auth '23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP'
OpenWhisk can also be installed on a Kubernetes cluster. You can use a managed Kubernetes cluster provisioned from a public cloud provider (e.g., AKS, EKS, IKS, GKE), or a cluster you manage yourself. Additionally for local development, OpenWhisk is compatible with Minikube, and Kubernetes for Mac using the support built into Docker 18.06 (or higher).
To get started:
git clone https://github.com/apache/openwhisk-deploy-kube.git
Then follow the instructions in the OpenWhisk on Kubernetes README.md.
Browse the documentation to learn more. Here are some topics you may be interested in:
Report bugs, ask questions and request features here on GitHub.
You can also join the OpenWhisk Team on Slack https://openwhisk-team.slack.com and chat with developers. To get access to our public Slack team, request an invite https://openwhisk.apache.org/slack.html.
The OpenWhisk system is built from a number of components. The picture below groups the components by their GitHub repos. Please open issues for a component against the appropriate repo (if in doubt just open against the main openwhisk repo).
This diagram depicts the steps which take place within Openwhisk when an action is invoked by the user: