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
|
Fission is a fast serverless framework for Kubernetes with a focus on
|
||||||
developer productivity and high performance. See http://fission.io
|
developer productivity and high performance.
|
||||||
for more.
|
|
||||||
|
|
||||||
Fission operates on just code: you don't deal with Docker or
|
Fission operates on _just code_: Docker and Kubernetes are abstracted
|
||||||
Kubernetes, they're abstracted away.
|
away.
|
||||||
|
|
||||||
We're built on Kubernetes because we think any non-trivial app will
|
Fission is extensible to any language. It currently supports NodeJS
|
||||||
use a combination of serverless functions and more conventional
|
and Python, with more languages coming soon.
|
||||||
microservices, and Kubernetes is a great framework to bring these
|
|
||||||
together seamlessly.
|
100msec cold start
|
||||||
|
------------------
|
||||||
|
|
||||||
Fission maintains a pool of "warm" containers that each contain a
|
Fission maintains a pool of "warm" containers that each contain a
|
||||||
small dynamic loader. When a function is first called,
|
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
|
loaded. This pool is what makes Fission fast: cold-start latencies
|
||||||
are typically about 100msec.
|
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
|
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
|
An _environment_ is a container with a webserver and dynamic loader
|
||||||
for functions. Today, Fission comes with NodeJS and Python
|
for functions. Today, Fission comes with NodeJS and Python
|
||||||
environments and you can also add your own. So for example if you
|
environments. You can also add your own: for example, if you want to
|
||||||
want to add some binaries to your Python image and call them from your
|
add a binary to your Python image, you can edit the Python
|
||||||
code, you can edit the Python environment's Dockerfile, rebuild it,
|
environment's Dockerfile, rebuild it, and add your new environment to
|
||||||
and add it to Fission.
|
Fission.
|
||||||
|
|
||||||
A _trigger_ is something that maps an event to a function; Fission
|
A _trigger_ is something that maps an event to a function; Fission
|
||||||
supports HTTP triggers today, with upcoming support for other types of
|
supports HTTP triggers today, with upcoming support for other types of
|
||||||
|
|||||||
Reference in New Issue
Block a user