OPCFoundation.NetStandard.Opc.Ua.Redundancy

v2.0.1-preview.200Latest Pre-release

net10.0.NETFramework4.8net8.0net9.0

OPC UA Redundancy shared CRDT building blocks (serializer + gossip key/value store)

OPCFoundation

NuGet Website LicenseCompare

Published

Oct 12, 2026

8d ago

Total Downloads

238

Install

dotnet add package OPCFoundation.NetStandard.Opc.Ua.Redundancy --version 2.0.1-preview.200

Download NuGet File Browse File Contents

Product	Versions
.NET	net10.0net8.0net9.0
Other	.NETFramework4.8

README

OPCFoundation.NetStandard.Opc.Ua.Redundancy

Shared replication building blocks for OPC UA redundancy, used by both Opc.Ua.Redundancy.Server and Opc.Ua.Redundancy.Client and built on the Opc.Ua.Redundancy seams in Opc.Ua.Core.

Eventually-consistent (AP): ByteStringCrdtSerializer and ReplicatedSharedKeyValueStore — an ISharedKeyValueStore that gossips state between replicas without a leader.
Strongly-consistent (CP): a Raft layer behind the IRaftConsensus seam — RaftSharedKeyValueStore (linearizable CompareAndSwapAsync + WatchAsync) and RaftLeaderElection (native single-leader election). The DI default is a single-node RaftCs replica via DefaultRaftConsensus; InProcessRaftConsensus is a lighter deterministic in-process backend, and a multi-node RaftNode (NanoMsg transport + file WAL) plugs in for multi-pod clusters.
Hybrid: HybridSharedKeyValueStore serves bulk keys from the CRDT store and the strong keyspaces (single-use nonces, lease, election) from Raft, selected with RedundancyConsistencyMode.

See docs/HighAvailability.md (Consistency modes) for guidance.

Changes from Previous Version

No structural changes between v2.0.0-preview.200 and v2.0.1-preview.200.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.The published metadata declares 93 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.