Wherever processes must agree
Reach for Nodus whenever your service runs as more than one instance and needs to coordinate — electing a leader, messaging peers, detecting failure, or fanning work across the cluster.
Six things Nodus makes easy
Each of these is a distributed-systems problem you would otherwise solve by hand or by adding another piece of infrastructure.
Cluster-aware services
Give any multi-instance service a live view of its peers, a shared leader, and a way to message members directly — the foundation Zaris itself clusters on.
Leader-only singletons & schedulers
Run a cron-like job on exactly one instance, gated on IsSelf, and have a survivor take over automatically at a higher epoch when the leader fails.
Failure detection & self-healing membership
Heartbeats and a suspicion window evict dead peers and admit new ones, keeping the cluster accurate through crashes and restarts.
Typed messaging & request-reply
Address a specific peer, send it work, and await a typed answer — or broadcast to everyone — over a persistent, prioritized transport.
Cache & peer invalidation
Broadcast an eviction to every member the instant a value changes, so no instance serves a stale entry.
Work distribution across nodes
Let a coordinator fan chunks of work across live members and aggregate the results — exactly what the shipped cluster-coordination sample does.
When Nodus fits
You run more than one instance
The moment a service scales past one process, it needs to know its peers and agree on who does what. That is precisely the gap Nodus fills.
You want to avoid another cluster
If standing up ZooKeeper, etcd or Consul feels like too much for the coordination you actually need, Nodus gives you membership and leadership as a library instead.
You are already on .NET
Nodus is a native .NET dependency with typed messages and events — no wire-format glue, no polyglot sidecar, no separate runtime.
Coordinate your cluster with Nodus
Membership, leadership, messaging and failure detection — in one embedded dependency.