Skip to main content

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

Redis-style collections, native to Zaris and replicated like every other key.

5 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.

Native Data Structures in .NET — Hashes, Lists, Sets, Sorted Sets — screen 1 — Zaris 2.0.0 stores collections, not just values. Hashes model a record, lists are ordered queues, sets hold unique members, and a sorted set is a live leaderboard — all with the Redis commands you know.

Native Data Structures in .NET — Hashes, Lists, Sets, Sorted Sets — screen 2 — Every one of these is a single logical value that lives on its owning partition and is replicated at replication factor two — exactly as durable and available as a plain key.

Native Data Structures in .NET — Hashes, Lists, Sets, Sorted Sets — screen 3 — From .NET you reach them through the typed client — client.Hashes, client.Lists, client.SortedSets; from any other language, the same collections answer over the Redis protocol.

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

Drop-in Redis — Point StackExchange.Redis at Zaris

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