.NEXT Raft alternatives and similar packages

Based on the "Distributed Computing" category.
Alternatively, view .NEXT Raft alternatives based on common mentions on social networks and blogs.

Akka.net

9.1 9.3 L3 .NEXT Raft VS Akka.net

Canonical actor model implementation for .NET with local + distributed actors in C# and F#.
protoactor-dotnet

7.3 8.3 .NEXT Raft VS protoactor-dotnet

Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin

The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

Promo workos.com

.NET port of LMAX Disruptor

6.8 7.2 .NEXT Raft VS .NET port of LMAX Disruptor

Port of LMAX Disruptor to .NET
IdGen

6.4 5.4 L5 .NEXT Raft VS IdGen

Twitter Snowflake-alike ID generator for .Net
Orleankka

5.1 7.2 L5 .NEXT Raft VS Orleankka

Functional API for Microsoft Orleans http://orleanscontrib.github.io/Orleankka
Zebus

4.5 7.0 L5 .NEXT Raft VS Zebus

A lightweight Peer to Peer Service Bus
MBrace

3.9 0.0 .NEXT Raft VS MBrace

MBrace Core Libraries & Runtime Foundations
FsShelter

2.1 0.0 L2 .NEXT Raft VS FsShelter

Author Apache Storm topologies with F# using statically-typed streams
Online Store Modular Monolith

1.7 7.8 .NEXT Raft VS Online Store Modular Monolith

🛒 Implementing an “online store” modular monolith application with domain-driven design and CQRS with using in-memory message broker based on .Net Core.

* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.

Do you think we are missing an alternative of .NEXT Raft or a related project?

README

.NEXT Raft Suite is a set of libraries for building clustered microservices:

DotNext.Net.Cluster contains cluster programming model, transport-agnostic implementation of Raft algorithm, TCP and UDP transport
DotNext.AspNetCore.Cluster is a concrete implementation of Raft algorithm on top of DotNext.Net.Cluster library for building ASP.NET Core applications. The transport for Raft messages is HTTP 1.1 and HTTP/2. TLS is also supported.

The list of supported features:

Network transport: TCP, UDP, HTTP 1.1, HTTP/2
High-performance, general-purpose Persistent Write-Ahead Log supporting log compaction
Replication of log entries across cluster nodes
Tight integration with ASP.NET Core framework
Friendly to Docker/LXC/Windows containers, e.g. port mapping between the host and the container
Everything is extensible
- Custom write-ahead log
- Custom network transport

Useful links: