ra

Erlang/OTP doesn't handle leader election, and by itself is bad at handling netsplits. There is https://github.com/rabbitmq/ra which is a Raft implementation in Erlang that is Jepsen-tested. You could use it to build "etcd in Erlang", or https://github.com/rabbitmq/khepri which is built on top of Ra.

Just to add to this, there are some implementations of things like consensus algorithms in Erlang such as Ra: https://github.com/rabbitmq/ra

ra for those interested: https://github.com/rabbitmq/ra ("A Raft implementation for Erlang and Elixir that strives to be efficient and make it easier to use multiple Raft clusters in a single system.") Used by RabbitMQ for quorum queues + Khepri (the new metadata store)

You may find these interesting... - "The Onion Layer Theory" https://learnyousomeerlang.com/building-applications-with-ot... - "On Erlang, State and Crashes" http://jlouisramblings.blogspot.com/2010/11/on-erlang-state-... - "Why Restarting Works" https://ferd.ca/the-zen-of-erlang.html (search for "Heisenbug") > you should store the state in the external system Disk works too, but if you're multi-node this means you now have a distributed database embedded in your system, which may or may not be your goal :) RabbitMQ does this, they developed a library for "persistent, fault-tolerant and replicated state machines" based on Raft: https://github.com/rabbitmq/ra.

RabbitMQ also made Ra[0], an Erlang implementation of Raft[1] [0] https://github.com/rabbitmq/ra [1] https://raft.github.io/

Has anyone approached Jepsen about running an analysis on the Erlang Ra implementation? I believe they've been running Jepsen tests internally, just curious if they're thinking about getting an official analysis at some point. Thanks for all that you folks do!! * https://github.com/rabbitmq/ra

> and despite its excellent concurrency characteristics the BEAM still lacks basics such as a battle-tested raft implementation. A couple of years ago the RabbitMQ team has published a raft library[1] which they use in their implementation of persistent queues. It has a flexible API and implementing your own state machines is quite straightforward, as it follows the OTP gen_* behaviour paradigm. And by now, I'd say it's pretty well battle-tested. [1] https://github.com/rabbitmq/ra

Ok let's talk concrete implementation. Rust: https://github.com/pingcap/raft-rs LOC: 15417 Erlang: https://github.com/rabbitmq/ra LOC: 18012 Lines of code is not the only metric. I'm actually really curious about Erlang and Elixir but to be honest I do like type systems a lot. I also like the idea of idk...having one language for my os, db, front-end.