Functions
The compute unit on Gigadrive Network, and the settings that decide how it runs, scales, and is billed.
A Function is the compute unit on Gigadrive Network. Every request your application serves, every WebSocket connection it holds open, and every response it streams runs inside one.
You declare Functions in gigadrive.yaml, or let framework detection declare them for you. The following settings change how a Function behaves at runtime; nothing here affects your build.
The identifiers you can set, and what each one expects your code to look like.
Memory and CPUSet memory per Function. CPU is fixed at one core.
Max durationHow long a single invocation may run, and what a timeout looks like to the client.
ConcurrencyHow one Function handles many requests at the same time.
StreamingResponse bodies reach the client as your code produces them.
WebSocketsLong-lived connections, their lifetime, and keeping a client on one target.
Sticky sessionsPinning every request that shares a key to one copy of a Function.
Cron jobsInvoking a Function on a schedule.
Function limitsRequest and response ceilings, and the status codes behind a rejected request.
