viewstamped-replication-made-famous

...and there's also an open bug bounty so if you think that Zig is not a meaningful improvement over C in terms of safety, it's certainly going to be easy money for you :^) https://github.com/tigerbeetledb/viewstamped-replication-mad...

"I assume you've followed Jespen?" Yes! You might also want to check out autonomous deterministic testing, which is like Jepsen, but where you can explore many more state spaces by speeding up time, and where you can replay any distributed bugs instantly, just by replaying a seed. This is a brilliant talk on these techniques: FoundationDB — How I Learned to Stop Worrying and Trust the Database — https://www.youtube.com/watch?v=OJb8A6h9jQQ I also work on a distributed database called TigerBeetle [1] where we use these new techniques. You can run our simulation tests yourself even. It's as simple as cloning the repo and running "scripts/vopr.sh", and let me know if you want a tour! These testing techniques work so well that we've been running a bug bounty challenge with awards up to $8192 for anyone who can find a way to break it or crash i

Here's the link to the $20k consensus challenge that was announced towards the end of the episode: https://github.com/coilhq/viewstamped-replication-made-famou...

Thanks for this awesome list. Coincidentally, we've just launched a $20k consensus challenge for Viewstamped Replication: https://github.com/coilhq/viewstamped-replication-made-famou... We don't implement the Reconfiguration Protocol yet which I believe is the correctness violation found by Ports et al.

As an example of this in distributed systems: There's a classic metastability issue in probably most implementations of state machine replication protocols such as Raft, where a lagging follower, if it sees an op that's newer than what it's expecting, must first repair and catch up its state (FIFO repair) before it can ACK back to the leader. Apart from introducing latency in the critical path, this can lead to really bad queueing behavior where the lagging follower queues the latest request from the leader while it first catches up, but because this catch up can take seconds or minutes, in that time the pending request queue has also overflowed, and now we're back to state transfer catch up all over again, a vicious cycle. However, there is a new approach (LIFO repair) that we developed for TigerBeetle [1] to eliminate this bimodality, m