Ta-Ching ChenandGitHub
b8311d43ce
When a function with executor type newdeploy got created, Newdeploy is expected to create deployment/HPA/service for it and insert serviceEntry to the cache for later use. Once clients call the function, newdeploy returns the serviceEntry to the router. However, the log shows that the newdeploy was unable to find the entry and prints "Resource not found - key 'xxx' not found". The root cause is that the informer controller instead of processing items in parallel, it dispatches XXFunc to process items one by one. So if there is any problem during the creation of the kubernetes resource, it takes a longer time to process the next item and hence the serviceEntry was not inserted before clients call the function. This PR lets the newdeploy to process items in extra goroutines instead of blocking the process loop. It's a workaround to solve the problem above, we should consider using workqueue to solve it in the future.
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.
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 and documentation
You can learn more about Fission and get started from Fission Docs.
- See the installation guide for installing and running Fission.
- See the troubleshooting guide for debugging your functions and Fission installation.
Contributing
Building Fission
See the compilation guide.
Contact
Fission is a project by many contributors.
Community meeting
A regular community meeting takes place every other Thursday at 08:30 AM PT (Pacific Time). Convert to your local timezone.
Official Releases
Official releases of Fission can be found on the releases page. Please note that it is strongly recommended that you use official releases of Fission, as unreleased versions from the master branch are subject to changes and incompatibilities that will not be supported in the official releases. Builds from the master branch can have functionality changed and even removed at any time without compatibility support and without prior notice.
Licensing
Fission is under the Apache 2.0 license.