Deploy on Strata Documentation

Single-node deployment

Mon, 01 Jan 0001 00:00:00 +0000

Single-node Strata#

A single-node deployment runs one strata process. It is the simplest shape Strata ships and the recommended starting point for labs, evaluation, and single-tenant pilots. The gateway is HTTP-stateless — durability lives in the metadata + data backends — so a single replica is not an HA shape: the box is the SPOF for HTTP traffic. For HA, see Multi-replica cluster.

Prerequisites#

One Linux host (or a macOS workstation for dev).
Docker (for the full stack) or Go 1.23+ (for the in-memory smoke).
2 vCPU + 1 GiB RSS baseline (see Sizing below).

The pure-memory path needs no other software. The Cassandra-backed path needs cassandra:5.0 reachable on :9042. The full stack (Cassandra + RADOS) is bootstrapped from the bundled compose file.

Docker Compose

Mon, 01 Jan 0001 00:00:00 +0000

Docker Compose deployment#

The bundled deploy/docker/docker-compose.yml is the canonical reference shape for a Strata stack on one host. Bare docker compose up -d brings up the TiKV-default 2-replica lab (PD + TiKV + ceph + ceph-b + strata-a + strata-b + nginx LB + prometheus + grafana). The Cassandra-backed regression lab lives under --profile cassandra so an operator can make up-cassandra to validate the Cassandra meta backend side by side.

Multi-replica cluster

Mon, 01 Jan 0001 00:00:00 +0000

Multi-replica Strata cluster — operator guide#

Strata’s gateway is stateless. Replicas don’t form a quorum among themselves; the storage layer (TiKV / RADOS) provides durability + consistency. A single replica is therefore a single point of failure for HTTP traffic — not for data. Running ≥2 replicas behind a load balancer is the minimum HA shape.

This page covers the bare-default 2-replica TiKV lab (two TiKV-backed replicas behind nginx at host :9999) — the reference shape for multi-replica deployments. Same wiring works for 3+ replicas in production.

Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes deployment#

Strata on Kubernetes is a stateless gateway tier in front of external metadata (TiKV or Cassandra) and object-data (RADOS or S3) clusters. Pods are interchangeable — no PVCs, no per-pod storage, no quorum among gateways. Scale horizontally with kubectl scale; durability lives in the storage tier.

This page walks through the worked example committed under deploy/k8s/ — a 3-replica Deployment + Service + ConfigMap + Secret + Ingress aimed at a production-shaped cluster. A Helm chart ships alongside at deploy/helm/strata/.