Skip to main content
← All videos

Getting Started — a Distributed Cache for .NET in Minutes

Point a plain .NET app at a real, replicated cluster in the cloud — and watch reads and writes land live.

5 minWatch on YouTube ↗

Watch it, or read it

The full walkthrough below — every screen from the video, with the narration transcribed. Skim it, search it, or read it in your own language.

Getting Started — a Distributed Cache for .NET in Minutes — screen 1
Getting started with Zaris — a distributed cache for .NET. In a few minutes we'll point a plain .NET app at a real, replicated cluster running in the cloud, and watch reads and writes land live in the console.
Getting Started — a Distributed Cache for .NET in Minutes — screen 2
Here's a four-node Zaris cluster running in Azure. The console shows every node healthy, replication factor two, and the data sharded into partitions — each partition with a primary and a replica on a different machine.
Getting Started — a Distributed Cache for .NET in Minutes — screen 3
The Nodes view walks the topology — the four pods, their ages and roles. This is a highly-available cluster: lose a node and its replicas keep serving without missing a beat.
Getting Started — a Distributed Cache for .NET in Minutes — screen 4
One store, sharded and replicated across those nodes. You don't place partitions by hand — Zaris maps them onto the cluster and rebalances as nodes come and go.
Getting Started — a Distributed Cache for .NET in Minutes — screen 5
Now, on a completely separate machine, a plain .NET app. No SDK ceremony — just one connection string, zaris colon slash slash, pointing at the cluster's endpoint.
Getting Started — a Distributed Cache for .NET in Minutes — screen 6
We run the Basic sample. It connects to the cluster, then writes a key. Set returns success — the write has landed on the owning partition.
Getting Started — a Distributed Cache for .NET in Minutes — screen 7
Then it reads the value straight back, sets a time-to-live, and deletes the key — the full key lifecycle, from a remote client, over the network.
Getting Started — a Distributed Cache for .NET in Minutes — screen 8
And it shows up live in the console. Connections tick up, the key count changes, throughput blips on the dashboard. This is a real remote client talking to a real cluster.
Getting Started — a Distributed Cache for .NET in Minutes — screen 9
Cross-platform, replicated, and as simple as a connection string. Add the Clustron.Zaris.Client package, point it at your cluster, and you're caching. Head to clustron.io to get started.

More videos

Securing a Distributed .NET Cache — Authentication & RBACTLS & Mutual TLS for a Distributed .NET CacheDistributed In-Memory Cache Architecture, ExplainedLinear Scaling Benchmark — 1 → 2 → 3 Nodes, LiveAny Language, One Store — Zaris Speaks RedisDrop-in Redis — Point StackExchange.Redis at ZarisNative Data Structures in .NET — Hashes, Lists, Sets, Sorted SetsRedis Streams, Native — Event Log + Consumer GroupsASP.NET Core Caching Without Redis — IDistributedCache & HybridCacheSurvive a Node Failure — Live HA FailoverElastic Scaling — Add Nodes LivePub/Sub in .NET — Cluster-Wide Messaging
Get startedSubscribe on YouTube