alihan/fn-serverless
1
0
Fork 0
mirror of https://github.com/fnproject/fn.git synced 2022-10-28 21:29:17 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated docs, cleaned things up, DRY's up function format stuff. (#688)

Browse Source 
* Updated docs, cleaned things up, DRY's up function format stuff.

* deleted files

* updated bad link
This commit is contained in:
Travis Reeder
2018-01-16 14:45:44 -08:00
committed by GitHub
parent e3a573d11a
commit 5a2602d42e
17 changed files with 164 additions and 352 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/developers/hot-functions.md Normal file
View File

@@ -0,0 +1,15 @@
# Hot functions
By default, Fn uses "cold functions" where every request starts up a new container, feeds it with the payload then sends the
answer back to the caller. You can expect an average start time of [300ms per execution]((https://medium.com/travis-on-docker/the-overhead-of-docker-run-f2f06d47c9f3#.96tj75ugb)) to start the function/container.
Hot functions improve performance by starting a function then keeping it alive to handle additional requests. This
makes it a bit trickier to use because you'll have to parse a stream of requests, but if you use an [FDK](fdks.md) it's
all taken care of for you, so you should probably use an FDK in most cases.
## Making a hot function
In your `func.yaml`, add `format: json`.
From there, we recommend using one of our [FDKs](fdks.md) to handle all the parsing and formatting. But if you'd like to learn
about the nitty gritty details, [check here](function-format.md).