Single decree is a write-once algorithm. You can't use the same instance again, for another update of the associated value.

So just replacing bizur' should "register" implementation with a single decree paxos won't be sufficient. You'll need to do something more elaborate (creating more instances as you go along).

This kind of instance management isn't required in bizur.

I'm not sure what's the overhead off all that, w.r.t. memory foot print. Since this overhead is paid for each bucket, it might accumulate to quite a bit.

Not really :) Please follow the links. "Paxos Made Simple" describes the write once variant, but it's possible to choose a new value for the next ballot cycles to make it rewritable.

Proof of the algorithm: http://rystsov.info/2015/09/16/how-paxos-works.html

Moreover, I built a system on top of it and extensively tested it with fault injections: https://github.com/gryadka/js.

It seems that GoshawkDB[1] uses the similar idea, Treode[2] used it too.

[1] https://goshawkdb.io/

[2] http://treode.github.io/design/

Very nice work! Indeed we've done similar stuff :) I haven't read it all yet, I'll comment back once I do.

Could you explain how Bizure compare to Gryadka. Are the performance tradeoff similar.