Sanket SudakeandGitHub
0a7dc70339
In Fission CI as well in a couple of scenarios, noticed Fission pods getting preempted when Function pods are getting created. As both Fission components and function pods have the same priority class fission component pods might get preempted. It to be recommended to set higher priority class for components such as Fission router, executor, controller so that Fission functioning doesn't get disrupted. Most of the Fission components work fine with restart except the executor. So user should set priorityClass for Fission executor. Signed-off-by: Sanket Sudake <sanketsudake@gmail.com>
Fission: Serverless Functions for Kubernetes
Fission is a fast serverless framework for Kubernetes with a focus on developer productivity and high performance.
Fission operates on just the code: Docker and Kubernetes are abstracted away under normal operation, though you can use both to extend Fission if you want to.
Fission is extensible to any language; the core is written in Go, and language-specific parts are isolated in something called environments (more below). Fission currently supports NodeJS, Python, Ruby, Go, PHP, Bash, and any Linux executable, with more languages coming soon.
Table of Contents
Performance: 100msec cold start
Fission maintains a pool of "warm" containers that each contain a small dynamic loader. When a function is first called, i.e. "cold-started", a running container is chosen and the function is loaded. This pool is what makes Fission fast: cold-start latencies are typically about 100msec.
Kubernetes is the right place for Serverless
We're built on Kubernetes because we think any non-trivial app will use a combination of serverless functions and more conventional microservices, and Kubernetes is a great framework to bring these together seamlessly.
Building on Kubernetes also means that anything you do for operations on your Kubernetes cluster — such as monitoring or log aggregation — also helps with ops on your Fission deployment.
Getting Started
# Add the stock NodeJS env to your Fission deployment
$ fission env create --name nodejs --image fission/node-env
# Create a function with a javascript one-liner that prints "hello world"
$ fission function create --name hello --env nodejs --code https://raw.githubusercontent.com/fission/examples/master/nodejs/hello.js
# Run the function. This takes about 100msec the first time.
$ fission function test --name hello
Hello, world!
Learn More
- Understand Fission Concepts.
- See the installation guide for installing and running Fission.
- You can learn more about Fission and get started from Fission Docs.
- See the troubleshooting guide for debugging your functions and Fission installation.
Contributing
Check out the contributing guide.
Sponsors
The following companies, organizations, and individuals support Fission's ongoing maintenance and development. If you are using/contributing to Fission, we would be happy to list you here, please raise a Pull request.
License
Fission is licensed under the Apache License 2.0 - see the LICENSE file for details