# Serverless Functions Orama Network runs serverless functions as sandboxed WebAssembly (WASM) modules. Functions are written in Go, compiled to WASM with TinyGo, and executed in an isolated wazero runtime with configurable memory limits and timeouts. Functions receive input via **stdin** (JSON) and return output via **stdout** (JSON). They can also access Orama services — database, cache, storage, secrets, PubSub, and HTTP — through **host functions** injected by the runtime. ## Quick Start ```bash # 1. Scaffold a new function orama function init my-function # 2. Edit your handler cd my-function # edit function.go # 3. Build to WASM orama function build # 4. Deploy orama function deploy # 5. Invoke orama function invoke my-function --data '{"name": "World"}' # 6. View logs orama function logs my-function ``` ## Project Structure ``` my-function/ ├── function.go # Handler code └── function.yaml # Configuration ``` ### function.yaml ```yaml name: my-function # Required. Letters, digits, hyphens, underscores. public: false # Allow unauthenticated invocation (default: false) memory: 64 # Memory limit in MB (1-256, default: 64) timeout: 30 # Execution timeout in seconds (1-300, default: 30) retry: count: 0 # Retry attempts on failure (default: 0) delay: 5 # Seconds between retries (default: 5) env: # Environment variables (accessible via get_env) MY_VAR: "value" ``` ### function.go (minimal) ```go package main import ( "encoding/json" "os" ) func main() { // Read JSON input from stdin var input []byte buf := make([]byte, 4096) for { n, err := os.Stdin.Read(buf) if n > 0 { input = append(input, buf[:n]...) } if err != nil { break } } var payload map[string]interface{} json.Unmarshal(input, &payload) // Process and return JSON output via stdout response := map[string]interface{}{ "result": "Hello!", } output, _ := json.Marshal(response) os.Stdout.Write(output) } ``` ### Building Functions are compiled to WASM using [TinyGo](https://tinygo.org/): ```bash # Using the CLI (recommended) orama function build # Or manually tinygo build -o function.wasm -target wasi function.go ``` ## Host Functions API Host functions let your WASM code interact with Orama services. They are imported from the `"env"` or `"host"` module (both work) and use a pointer/length ABI for string parameters. All host functions are registered at runtime by the engine. They are available to every function without additional configuration. ### Context | Function | Description | |----------|-------------| | `get_caller_wallet()` → string | Wallet address of the caller (from JWT) | | `get_request_id()` → string | Unique invocation ID | | `get_env(key)` → string | Environment variable from function.yaml | | `get_secret(name)` → string | Decrypted secret value (see [Managing Secrets](#managing-secrets)) | ### Database (RQLite) | Function | Description | |----------|-------------| | `db_query(sql, argsJSON)` → JSON | Execute SELECT query. Args as JSON array. Returns JSON array of row objects. | | `db_execute(sql, argsJSON)` → int | Execute INSERT/UPDATE/DELETE. Returns affected row count. | Example query from WASM: ``` db_query("SELECT push_token, device_type FROM devices WHERE user_id = ?", '["user123"]') → [{"push_token": "abc...", "device_type": "ios"}] ``` ### Cache (Olric Distributed Cache) | Function | Description | |----------|-------------| | `cache_get(key)` → bytes | Get cached value by key. Returns empty on miss. | | `cache_set(key, value, ttl)` | Store value with TTL in seconds. | | `cache_incr(key)` → int64 | Atomically increment by 1 (init to 0 if missing). | | `cache_incr_by(key, delta)` → int64 | Atomically increment by delta. | ### HTTP | Function | Description | |----------|-------------| | `http_fetch(method, url, headersJSON, body)` → JSON | Make outbound HTTP request. Headers as JSON object. Returns `{"status": 200, "headers": {...}, "body": "..."}`. Timeout: 30s. | ### PubSub | Function | Description | |----------|-------------| | `pubsub_publish(topic, dataJSON)` → bool | Publish message to a PubSub topic. Returns true on success. | ### Logging | Function | Description | |----------|-------------| | `log_info(message)` | Log info-level message (captured in invocation logs). | | `log_error(message)` | Log error-level message. | ## Managing Secrets Secrets are encrypted at rest (AES-256-GCM) and scoped to your namespace. Functions read them via `get_secret("name")` at runtime. ### CLI Commands ```bash # Set a secret (inline value) orama function secrets set APNS_KEY_ID "ABC123DEF" # Set a secret from a file (useful for PEM keys, certificates) orama function secrets set APNS_AUTH_KEY --from-file ./AuthKey_ABC123.p8 # List all secret names (values are never shown) orama function secrets list # Delete a secret orama function secrets delete APNS_KEY_ID # Delete without confirmation orama function secrets delete APNS_KEY_ID --force ``` ### How It Works 1. **You set secrets** via the CLI → encrypted and stored in the database 2. **Functions read secrets** at runtime via `get_secret("name")` → decrypted on demand 3. **Namespace isolation** → each namespace has its own secret store; functions in namespace A cannot read secrets from namespace B ## PubSub Triggers Triggers let functions react to events automatically. When a message is published to a PubSub topic, all functions with a trigger on that topic are invoked asynchronously. ### CLI Commands ```bash # Add a trigger: invoke "call-push-handler" when messages hit "calls:invite" orama function triggers add call-push-handler --topic calls:invite # List triggers for a function orama function triggers list call-push-handler # Delete a trigger orama function triggers delete call-push-handler ``` ### Trigger Event Payload When triggered via PubSub, the function receives this JSON via stdin: ```json { "topic": "calls:invite", "data": { ... }, "namespace": "my-namespace", "trigger_depth": 1, "timestamp": 1708972800 } ``` ### Depth Limiting To prevent infinite loops (function A publishes to topic → triggers function A again), trigger depth is tracked. Maximum depth is **5**. If a function's output triggers another function, `trigger_depth` increments. At depth 5, no further triggers fire. ## Function Lifecycle ### Versioning Each deploy creates a new version. The WASM binary is stored in **IPFS** (content-addressed) and metadata is stored in **RQLite**. ```bash # List versions orama function versions my-function # Invoke a specific version curl -X POST .../v1/functions/my-function@2/invoke ``` ### Invocation Logging Every invocation is logged with: request ID, duration, status (success/error/timeout), input/output size, and any `log_info`/`log_error` messages. ```bash orama function logs my-function ``` ## CLI Reference | Command | Description | |---------|-------------| | `orama function init ` | Scaffold a new function project | | `orama function build [dir]` | Compile Go to WASM | | `orama function deploy [dir]` | Deploy WASM to the network | | `orama function invoke --data ` | Invoke a function | | `orama function list` | List deployed functions | | `orama function get ` | Get function details | | `orama function delete ` | Delete a function | | `orama function logs ` | View invocation logs | | `orama function versions ` | List function versions | | `orama function secrets set ` | Set an encrypted secret | | `orama function secrets list` | List secret names | | `orama function secrets delete ` | Delete a secret | | `orama function triggers add --topic ` | Add PubSub trigger | | `orama function triggers list ` | List triggers | | `orama function triggers delete ` | Delete a trigger | ## HTTP API Reference | Method | Endpoint | Description | |--------|----------|-------------| | POST | `/v1/functions` | Deploy function (multipart/form-data) | | GET | `/v1/functions` | List functions | | GET | `/v1/functions/{name}` | Get function info | | DELETE | `/v1/functions/{name}` | Delete function | | POST | `/v1/functions/{name}/invoke` | Invoke function | | GET | `/v1/functions/{name}/versions` | List versions | | GET | `/v1/functions/{name}/logs` | Get logs | | WS | `/v1/functions/{name}/ws` | WebSocket invoke (streaming) | | PUT | `/v1/functions/secrets` | Set a secret | | GET | `/v1/functions/secrets` | List secret names | | DELETE | `/v1/functions/secrets/{name}` | Delete a secret | | POST | `/v1/functions/{name}/triggers` | Add PubSub trigger | | GET | `/v1/functions/{name}/triggers` | List triggers | | DELETE | `/v1/functions/{name}/triggers/{id}` | Delete trigger | | POST | `/v1/invoke/{namespace}/{name}` | Direct invoke (alt endpoint) | ## Example: Call Push Handler A real-world function that sends VoIP push notifications when a call invite is published to PubSub: ```yaml # function.yaml name: call-push-handler memory: 128 timeout: 30 ``` ```go // function.go — triggered by PubSub on "calls:invite" package main import ( "encoding/json" "os" ) // This function: // 1. Receives a call invite event from PubSub trigger // 2. Queries the database for the callee's device info // 3. Reads push notification credentials from secrets // 4. Sends a push notification via http_fetch func main() { // Read PubSub trigger event from stdin var input []byte buf := make([]byte, 4096) for { n, err := os.Stdin.Read(buf) if n > 0 { input = append(input, buf[:n]...) } if err != nil { break } } // Parse the trigger event wrapper var event struct { Topic string `json:"topic"` Data json.RawMessage `json:"data"` } json.Unmarshal(input, &event) // Parse the actual call invite data var invite struct { CalleeID string `json:"calleeId"` CallerName string `json:"callerName"` CallType string `json:"callType"` } json.Unmarshal(event.Data, &invite) // At this point, the function would use host functions: // // 1. db_query("SELECT push_token, device_type FROM devices WHERE user_id = ?", // json.Marshal([]string{invite.CalleeID})) // // 2. get_secret("FCM_SERVER_KEY") for Android push // get_secret("APNS_KEY_PEM") for iOS push // // 3. http_fetch("POST", "https://fcm.googleapis.com/v1/...", headers, body) // // 4. log_info("Push sent to " + invite.CalleeID) // // Note: Host functions use the WASM ABI (pointer/length). // A Go SDK for ergonomic access is planned. response := map[string]interface{}{ "status": "sent", "callee": invite.CalleeID, } output, _ := json.Marshal(response) os.Stdout.Write(output) } ``` Deploy and wire the trigger: ```bash orama function build orama function deploy # Set push notification secrets orama function secrets set FCM_SERVER_KEY "your-fcm-key" orama function secrets set APNS_KEY_PEM --from-file ./AuthKey.p8 orama function secrets set APNS_KEY_ID "ABC123" orama function secrets set APNS_TEAM_ID "TEAM456" # Wire the PubSub trigger orama function triggers add call-push-handler --topic calls:invite ```