Skip to main content

Drop-in Redis — Point StackExchange.Redis at Zaris

Keep your existing StackExchange.Redis code. Change one thing — the host — and you're on Zaris.

4 min

Coming soon

This walkthrough is in production. Subscribe on YouTube to catch it first.

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.

Drop-in Redis — Point StackExchange.Redis at Zaris — screen 1 — If your .NET app already talks to Redis through StackExchange.Redis, moving to Zaris isn't a rewrite. The only change is the endpoint — point the multiplexer at a Zaris node's Redis port.

Drop-in Redis — Point StackExchange.Redis at Zaris — screen 2 — Run it. It connects, writes, reads, sets a hash, expires a key — every call returns exactly what Redis would return.

Drop-in Redis — Point StackExchange.Redis at Zaris — screen 3 — What's underneath is different: the data is partitioned and replicated across the cluster at replication factor two, so a node can fail without losing your cache. Same client, a highly-available store behind it.

More videos

Getting Started — a Distributed Cache for .NET in Minutes

Securing a Distributed .NET Cache — Authentication & RBAC

TLS & Mutual TLS for a Distributed .NET Cache

Distributed In-Memory Cache Architecture, Explained

Linear Scaling Benchmark — 1 → 2 → 3 Nodes, Live

Any Language, One Store — Zaris Speaks Redis

Native Data Structures in .NET — Hashes, Lists, Sets, Sorted Sets

Redis Streams, Native — Event Log + Consumer Groups

ASP.NET Core Caching Without Redis — IDistributedCache & HybridCache

Survive a Node Failure — Live HA Failover

Elastic Scaling — Add Nodes Live

Pub/Sub in .NET — Cluster-Wide Messaging

Get started Subscribe on YouTube