News for hackers. Stuff that matters.
Re:Dqlite – High-Availability SQLite by hardwaresofton on Friday August 30, 2019 @06:00AM (#20837181)
There's one more big distinction, rqlite's replication is command based [0] where as dqlite is/was WAL frame-based -- so basically one ships the command and the other ships WAL frames. This distinction means that non-deterministic commands (ex. `RANDOM()`) will work differently.

It looks like dqlite's documentation has changed -- for some reason frames are no longer mentioned anywhere[2]. So maybe this isn't the case any more, but this was once the biggest differentiator for me.

[0]: https://github.com/rqlite/rqlite/#limitations

[1]: https://webcache.googleusercontent.com/search?q=cache:p1XBgh...

[2]: https://github.com/canonical/dqlite/commit/35ea7cd56e93a36c5...

Re:Dqlite – High-Availability SQLite by rlpb on Friday August 30, 2019 @06:29AM (#20837293)
> dqlite is/was WAL frame-based...maybe this isn't the case any more

According to https://github.com/canonical/dqlite/blob/master/doc/faq.md this is still the case.

Re:Dqlite – High-Availability SQLite by hardwaresofton on Friday August 30, 2019 @06:32AM (#20837310)
Ahhhh thank you -- that information just got pushed into the FAQ -- I was thinking "surely they didn't just remove this information" but didn't look hard enough at all. Direct link:

https://github.com/canonical/dqlite/blob/master/doc/faq.md#h...

Re:Dqlite – High-Availability SQLite by sansnomme on Friday August 30, 2019 @04:39PM (#20842467)
Can you give an example of how the specific differences may occur?
Re:Dqlite – High-Availability SQLite by rntksi on Friday August 30, 2019 @08:55PM (#20843992)
If you do command-based replication, an insert or update that uses RANDOM() would have to be handled differently, lest you have differing values due to each member of the cluster evaluating and producing different values. (Anything that is an impure function basically will have that problem)