Blueprint · Go WebAssembly Function

Go WebAssembly HTTP Function Starter (func-go-minimal)

Minimal Go function: a single HTTP handler returning 'hello world'. Scaffold a Go HTTP function compiled to WebAssembly, wired into stack.json and the KERNSTACK gateway in one CLI command.

Functions (WASM)Edge Gateway stack.json IaC

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

One-Command CLI Initialization

CLI Command func-go-minimal

kernstack add function --name api --blueprint func-go-minimal

Why start with a Go WebAssembly function on the Software Lifecycle Cloud

The func-go-minimal blueprint gives product teams and coding agents a clean, deterministic entry point for HTTP APIs, webhook receivers,scheduled cron triggers, and table change-stream handlers on KERNSTACK.

Unlike hyperscaler functions that spin up heavyweight microVMs and require separate API Gateway, IAM role, and CloudWatch log-group declarations, a KERNSTACK function is compiled to WebAssembly and scheduled directly on European bare metal.

WebAssembly sandbox startup with strict memory isolation
Direct access to KERNSTACK Tables, Buckets, Search, and Secrets via the Go SDK
Supports HTTP routes, WebSockets, cron schedules, and table change streams in stack.json

How people and agents extend this blueprint

Once scaffolded with kernstack add function, the blueprint vendors the typed Go SDK into .kernstack/sdk-go-v1 so local IDE autocompletion and agent harnesses such as Cursor or Claude Code can immediately inspect every method.

Before any change reaches staging or production, kernstack plan diffs the function signature, routes, and schedules against the live project graph.

What the Go function scaffold actually contains

func-go-minimal compiles a Go HTTP handler to WebAssembly. The handler starts in a short-lived sandbox, reads the request the gateway already authenticated, and returns JSON without a companion API gateway, a per-function IAM role, or a separate log group. Teams use it for webhooks, cron ticks, and table change handlers that should cost nothing while idle.

The vendored Go SDK exposes tables, buckets, search, inference, and secrets as in-process calls. A coding agent can read those method names from the module cache. The sandbox isolates the handler, so a runaway allocation stops in that sandbox rather than on a shared VM. The first edit most squads make is replacing the status payload with the domain response their client already expects.

Starter Code — func-go-minimal go

package main

import (
  "context"
  "net/http"

  "github.com/coding-berlin/kernstack-sdk-go/sdk_functions/sdk_functions_runtime"
  "github.com/coding-berlin/kernstack-sdk-go/sdk_functions/sdk_types_functions"
)

func handler(ctx context.Context, req sdk_types_functions.FunctionInvokeRequest) (sdk_types_functions.FunctionInvokeResponse, error) {
  return sdk_types_functions.FunctionInvokeResponse{
    RequestID:  req.RequestID,
    StatusCode: http.StatusOK,
    Body:       []byte("hello world"),
  }, nil
}

func main() {
  sdk_functions_runtime.RunWithContext(context.Background(), handler)
}

stack.json — func-go-minimal plan · deploy

{
  "stack": { "target": "app.prod" },
  "gateway": {
    "routes": [
      {
        "name": "api",
        "type": "http",
        "target": { "kind": "function", "name": "api" }
      }
    ]
  },
  "resources": {
    "functions": [
      { "name": "api" }
    ]
  }
}

FAQ

Frequently asked questions

How do I scaffold the func-go-minimal template?

Run kernstack add function --name api --blueprint func-go-minimal inside any initialized KERNSTACK project, then run kernstack plan and kernstack deploy.

Can a Go function connect to Tables and Search indexes?

Yes. The vendored Go SDK ships typed clients for tables, buckets, search, and inference, and credentials reach the handler through the platform-injected environment — nothing to configure in the repository.

When should I choose a Go Function versus a Go Worker?

Choose a Go Function for request-response APIs, webhooks, cron jobs, and change-stream triggers. Choose a Go Worker (work-go-minimal) for long-running background processes or mounted bucket volumes.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →