Skip to content

Zaris 0.9.0

Choose a tag to compare

@zeroheartbeat zeroheartbeat released this 05 Aug 13:54
· 5 commits to main since this release

Zaris 0.9.0 — Generally Available

Zaris is a distributed, in-memory key/value store for .NET — fast, replicated, and operable from a browser,
PowerShell, or your app. This release marks Zaris's general availability: production-ready, cross-platform,
and now with commercial support.

Distributed replication & high availability

  • Partitioned, replicated storage. Data is split into partitions, each kept on multiple nodes at a
    configurable replication factor.
  • Automatic failover & self-healing. Lose a node and the cluster keeps serving; replicas are restored
    automatically once capacity returns.
  • Elastic scaling. Add or remove nodes and the partition map grows and rebalances — no downtime.
  • Sizing for durability: each partition needs RF distinct instances, so run enough nodes for every partition
    to reach RF (on Kubernetes, one node per pod → a pod count that's a multiple of RF; RF2 → an even count).

Web Console

A browser-based management UI for your cluster:

  • Live cluster, node, and partition health, throughput and latency metrics, and active connections.
  • Store management — create, start, scale, and inspect stores.
  • Encryption (TLS/CA) management — download, import, and verify certificates with guided, plain-language steps.
  • Workspaces for connecting to and switching between clusters.

First-class PowerShell tooling

Redesigned AdminShell and ClientShell modules:

  • Workspace-based connectionsNew-ZrWorkspace / Use-ZrWorkspace (no more manager wiring).
  • Store lifecycle & scalingNew-ZrStore, Start-ZrStore, Add-ZrServer / Remove-ZrServer.
  • Live operationsWatch-ZrStoreMetrics with operator-first metric ordering, clearer connection errors,
    and automatic CA fetch.

A cleaner, richer client API

  • Connection strings everywhere — one API across in-process, remote, Docker, and Kubernetes:
    zaris://host:7861/store (or zariss://… for TLS), with comma-separated seed hosts and failover, and tokens
    supplied safely via env: / file:.
  • Rich data operations — get / put / delete, compare-and-swap, bulk and batch, scan and search, prefix
    operations, transactions, leases, leader election, distributed counters, rate limiting, and a distributed job
    queue.
  • ASP.NET Core caching — drop-in IDistributedCache and HybridCache providers.
  • Resilient clients — topology-aware routing with automatic retry and reconnection.

Runs everywhere: Windows, Linux, Docker, Kubernetes

  • Windows — one installer for the server, Management Service, Web Console, and PowerShell modules.
  • Linux & Docker — published container images, plus a one-command Docker Compose cluster.
  • Kubernetes — an official Helm chart with a StatefulSet, convergence-gated readiness, a
    PodDisruptionBudget, and drain-safe termination; published images; external (out-of-cluster) client access; TLS.

Security & observability

  • TLS for both client and node-to-node traffic, with pluggable CA trust — auto-issued, bring-your-own-CA,
    intermediate-signed, or pre-issued certificates — and token-based authentication.
  • OpenTelemetry — export traces, metrics, and logs to any OTLP-compatible backend, all config-gated.

Install

NuGet

dotnet add package Clustron.Zaris.Client --version 0.9.0

Windows — download clustron-zaris-0.9.0-win-x64.zip below (verify against SHA256SUMS.txt).

Docker

docker pull clustron/zaris-node:0.9.0
docker pull clustron/zaris-manager:0.9.0

Kubernetes (Helm)

helm install zaris oci://registry-1.docker.io/clustron/zaris --version 0.9.0 \
  -n zaris --create-namespace

Support

Zaris is open and free to run. Commercial support plans and professional services are available for teams
running Zaris in production — see clustron.io/support.

Telemetry & privacy

Zaris reports lightweight usage telemetry to help guide the roadmap:

  • Install events are recorded on first run per install, including basic host identity (hostname / OS user /
    domain) and a server-derived coarse location (country / region / city).
  • Feature-usage events record which control-plane features get used — anonymous, and deduplicated per day.

Opt out completely by setting CLUSTRON_TELEMETRY=false (also 0 / no) in the node or manager environment.


License: Business Source License 1.1 (BSL 1.1).