readme updates
This commit is contained in:
@@ -2,16 +2,16 @@ Fission: Serverless Functions for Kubernetes
|
||||
============================================
|
||||
|
||||
Fission is a fast serverless framework for Kubernetes with a focus on
|
||||
developer productivity and high performance. See http://fission.io
|
||||
for more.
|
||||
developer productivity and high performance.
|
||||
|
||||
Fission operates on just code: you don't deal with Docker or
|
||||
Kubernetes, they're abstracted away.
|
||||
Fission operates on _just code_: Docker and Kubernetes are abstracted
|
||||
away.
|
||||
|
||||
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.
|
||||
Fission is extensible to any language. It currently supports NodeJS
|
||||
and Python, with more languages coming soon.
|
||||
|
||||
100msec cold start
|
||||
------------------
|
||||
|
||||
Fission maintains a pool of "warm" containers that each contain a
|
||||
small dynamic loader. When a function is first called,
|
||||
@@ -19,8 +19,16 @@ 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.
|
||||
|
||||
Fission is extensible to any language. It currently supports NodeJS
|
||||
and Python, with more languages coming soon.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
Fission Concepts
|
||||
================
|
||||
@@ -29,10 +37,10 @@ A _function_ is a piece of code with an entry point.
|
||||
|
||||
An _environment_ is a container with a webserver and dynamic loader
|
||||
for functions. Today, Fission comes with NodeJS and Python
|
||||
environments and you can also add your own. So for example if you
|
||||
want to add some binaries to your Python image and call them from your
|
||||
code, you can edit the Python environment's Dockerfile, rebuild it,
|
||||
and add it to Fission.
|
||||
environments. You can also add your own: for example, if you want to
|
||||
add a binary to your Python image, you can edit the Python
|
||||
environment's Dockerfile, rebuild it, and add your new environment to
|
||||
Fission.
|
||||
|
||||
A _trigger_ is something that maps an event to a function; Fission
|
||||
supports HTTP triggers today, with upcoming support for other types of
|
||||
|
||||
Reference in New Issue
Block a user