Go · Tables Implementation

Go with KERNSTACK tables

Go plus Tables is the platform’s home pairing: Go handlers (functions or a binary worker) read and write tables through the typed Go SDK, with the table’s key design declared in the same file as the code that depends on it. Access keys inside deployed code come from the injected environment — no credentials in the repository.

NoSQL Tables stack.json IaC

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

Go Tables

The table declaration is a design act the Go code then trusts: key_name and sortkey_name encode the access patterns (orders by customer, newest first), and secondary indexes declare the second read honestly. Seed files at seed/tables/orders.json make local serves and previews start from representative data.

Inside deployed functions and workers, the SDK client is built from the injected access key set (KERNSTACK_ACCESS_KEY_ID, KERNSTACK_ACCESS_KEY_SECRET, KERNSTACK_DZONE) — the same code runs locally with your own key set, so there is no environment-specific credential plumbing to maintain.

Writes can announce themselves: add change_stream to the table and a Go function receives batched change records. The pair (Go handler, streamed table) covers a large share of event-driven product backends without a queue product entering the picture.

CLI

Plan Go Tables, then deploy.

Terminal — CLI workflow kernstack cli

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

Docs for Go Tables. Tables on the platform.

go-tables.txt Go

kernstack add function --name api
# declare the table in stack.json (below), then use the vendored SDK:
#   aks, _ := auth_sdk_accesskey.GetDefaultAccessKeySet()  // env-injected in deploys
#   client := sdk_client_tables.NewClient(...)
kernstack plan && kernstack deploy

stack.json — Go + tables plan · deploy

{
  "resources": {
    "functions": [{ "name": "api" }],
    "tables": [{ "name": "orders", "key_name": "customer_id", "key_type": "S",
      "sortkey_name": "ts", "sortkey_type": "N", "indexes": [] }]
  }
}

FAQ

Frequently asked questions

How does Go code authenticate to tables?

With an access key set passed to the typed client. In deploys the platform injects the key set as environment variables; locally you supply your own. Keys never live in source.

What does table access cost from Go?

The table’s storage at 0.04 credits per GB-hour, plus the GiB-seconds of the Go code doing the reading and writing. There are no per-unit read/write meters to model.

Can a Go worker use tables too?

Yes. Binary workers use the same SDK and the same declarations; the function/worker choice is about duration and triggers, not about data access.

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 →