FlowG, a low-code log management software, is transitioning from a standalone server to a distributed system to address user demands for replication, high availability, and redundancy. The project considered Raft and Paxos protocols for consensus, but found them unsuitable due to their unavailability during leader election. Instead, they chose the SWIM protocol and aim for eventual consistency using Conflict-free Replicated Data Types (CRDTs). The replication layer is still in development, with ongoing explorations into optimizing performance and reliability.
Sort: