mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
Cleaning up docs
This commit is contained in:
committed by
Chad Arimura
parent
acb2af526b
commit
d115ad6d45
127
docs/usage.md
Normal file
127
docs/usage.md
Normal file
@@ -0,0 +1,127 @@
|
||||
# Detailed Usage
|
||||
|
||||
This is a more detailed explanation of the main commands you'll use in Oracle Functions as a developer.
|
||||
|
||||
### Create an Application
|
||||
|
||||
An application is essentially a grouping of functions, that put together, form an API. Here's how to create an app.
|
||||
|
||||
```sh
|
||||
fn apps create myapp
|
||||
```
|
||||
|
||||
Or using a cURL:
|
||||
|
||||
```sh
|
||||
curl -H "Content-Type: application/json" -X POST -d '{
|
||||
"app": { "name":"myapp" }
|
||||
}' http://localhost:8080/v1/apps
|
||||
```
|
||||
|
||||
[More on apps](docs/apps.md).
|
||||
|
||||
Now that we have an app, we can route endpoints to functions.
|
||||
|
||||
### Add a Route
|
||||
|
||||
A route is a way to define a path in your application that maps to a function. In this example, we'll map
|
||||
`/hello` to a simple `Hello World!` function called `treeder/hello` which is a function we already made that you
|
||||
can use -- yes, you can share functions! The source code for this function is in the [examples directory](examples/hello/go).
|
||||
You can read more about [writing your own functions here](docs/writing.md).
|
||||
|
||||
```sh
|
||||
fn routes create myapp /hello -i treeder/hello
|
||||
```
|
||||
|
||||
Or using cURL:
|
||||
|
||||
```sh
|
||||
curl -H "Content-Type: application/json" -X POST -d '{
|
||||
"route": {
|
||||
"path":"/hello",
|
||||
"image":"treeder/hello"
|
||||
}
|
||||
}' http://localhost:8080/v1/apps/myapp/routes
|
||||
```
|
||||
|
||||
[More on routes](docs/routes.md).
|
||||
|
||||
### Calling your Function
|
||||
|
||||
Calling your function is as simple as requesting a URL. Each app has its own namespace and each route mapped to the app.
|
||||
The app `myapp` that we created above along with the `/hello` route we added would be called via the following
|
||||
URL: http://localhost:8080/r/myapp/hello
|
||||
|
||||
Either surf to it in your browser or use `fn`:
|
||||
|
||||
```sh
|
||||
fn call myapp /hello
|
||||
```
|
||||
|
||||
Or using a cURL:
|
||||
|
||||
```sh
|
||||
curl http://localhost:8080/r/myapp/hello
|
||||
```
|
||||
|
||||
### Passing data into a function
|
||||
|
||||
Your function will get the body of the HTTP request via STDIN, and the headers of the request will be passed in
|
||||
as env vars. You can test a function with the CLI tool:
|
||||
|
||||
```sh
|
||||
echo '{"name":"Johnny"}' | fn call myapp /hello
|
||||
```
|
||||
|
||||
Or using cURL:
|
||||
|
||||
```sh
|
||||
curl -H "Content-Type: application/json" -X POST -d '{
|
||||
"name":"Johnny"
|
||||
}' http://localhost:8080/r/myapp/hello
|
||||
```
|
||||
|
||||
You should see it say `Hello Johnny!` now instead of `Hello World!`.
|
||||
|
||||
### Add an asynchronous function
|
||||
|
||||
Oracle Functions supports synchronous function calls like we just tried above, and asynchronous for background processing.
|
||||
|
||||
Asynchronous function calls are great for tasks that are CPU heavy or take more than a few seconds to complete.
|
||||
For instance, image processing, video processing, data processing, ETL, etc.
|
||||
Architecturally, the main difference between synchronous and asynchronous is that requests
|
||||
to asynchronous functions are put in a queue and executed on upon resource availability so that they do not interfere with the fast synchronous responses required for an API.
|
||||
Also, since it uses a message queue, you can queue up millions of function calls without worrying about capacity as requests will
|
||||
just be queued up and run at some point in the future.
|
||||
|
||||
To add an asynchronous function, create another route with the `"type":"async"`, for example:
|
||||
|
||||
```sh
|
||||
curl -H "Content-Type: application/json" -X POST -d '{
|
||||
"route": {
|
||||
"type": "async",
|
||||
"path":"/hello-async",
|
||||
"image":"treeder/hello"
|
||||
}
|
||||
}' http://localhost:8080/v1/apps/myapp/routes
|
||||
```
|
||||
|
||||
Now if you request this route:
|
||||
|
||||
```sh
|
||||
curl -H "Content-Type: application/json" -X POST -d '{
|
||||
"name":"Johnny"
|
||||
}' http://localhost:8080/r/myapp/hello-async
|
||||
```
|
||||
|
||||
You will get a `call_id` in the response:
|
||||
|
||||
```json
|
||||
{"call_id":"572415fd-e26e-542b-846f-f1f5870034f2"}
|
||||
```
|
||||
|
||||
If you watch the logs, you will see the function actually runs in the background:
|
||||
|
||||

|
||||
|
||||
Read more on [logging](docs/logging.md).
|
||||
Reference in New Issue
Block a user