mirror of
https://github.com/openfaas/faas.git
synced 2025-06-10 09:16:48 +00:00
Create asynchronous.md
This commit is contained in:
parent
5f4c731df6
commit
59d02fa955
75
guide/asynchronous.md
Normal file
75
guide/asynchronous.md
Normal file
@ -0,0 +1,75 @@
|
||||
# Guide on Asynchronous processing
|
||||
|
||||
By default functions are accessed synchronously via the following route:
|
||||
|
||||
```
|
||||
$ http://gateway/function/{function_name}
|
||||
```
|
||||
|
||||

|
||||
|
||||
As of PR #131 asynchronous invocation is available for testing.
|
||||
|
||||
## Why use Asynchronous processing?
|
||||
|
||||
* Enable longer time-outs
|
||||
|
||||
* Process work whenever resources are available rather than immediately
|
||||
|
||||
* Consume a large batch of work within a few seconds and let it process at its own pace
|
||||
|
||||
## How does it work?
|
||||
|
||||
Here is a conceptual diagram
|
||||
|
||||

|
||||
|
||||
* [queue-worker](https://github.com/open-faas/nats-queue-worker)
|
||||
|
||||
## Deploy the Asynchronous stack
|
||||
|
||||
The reference implementation for asychronous processing uses NATS Streaming, but you are free to extend OpenFaaS and write your own [queue-worker](https://github.com/open-faas/nats-queue-worker).
|
||||
|
||||
Swarm:
|
||||
|
||||
```
|
||||
$ ./deploy_extended.sh
|
||||
```
|
||||
|
||||
K8s:
|
||||
|
||||
```
|
||||
$ kubectl -f delete ./faas.yml
|
||||
$ kubectl -f apply ./faas.async.yml,nats.yml
|
||||
```
|
||||
|
||||
## Call a function
|
||||
|
||||
Functions do not need to be modified to work asynchronously, just use this alternate route:
|
||||
|
||||
```
|
||||
$ http://gateway/async-function/{function_name}
|
||||
```
|
||||
|
||||
If you want the function to call another function or a different endpoint when it is finished then pass the `X-Callback-Url` header. This is optional.
|
||||
|
||||
```
|
||||
$ curl http://gateway/async-function/{function_name} --data-binary @sample.json -H "X-Callback-Url: http://gateway/function/send2slack"
|
||||
```
|
||||
|
||||
## Extend function timeouts
|
||||
|
||||
Functions have three timeouts configurable by environmental variables expressed in seconds:
|
||||
|
||||
HTTP:
|
||||
|
||||
* read_timeout
|
||||
* write_timeout
|
||||
|
||||
Hard timeout:
|
||||
|
||||
* exec_timeout
|
||||
|
||||
To make use of these just add them to your Dockerfile when needed as ENV variables.
|
||||
|
||||
> [Function watchdog reference](https://github.com/alexellis/faas/tree/master/watchdog)
|
Loading…
x
Reference in New Issue
Block a user