Testing consistency of rqlite

rqlite author here, happy to answer any questions. Many thanks to Nienke Eijsvogel, Ruben van Baarle and Daan de Graaf for executing this testing.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;rqlite&#x2F;rqlite" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rqlite&#x2F;rqlite</a>

Can you also auto-shard with rqlite, or is it only designed to distribute a single set of data among many SQLite instances?<p>EDIT: Looks like no: &quot;rqlite is about replicating a set of data, which has been written to it using SQL. The data is replicated for fault tolerance because your data is so important that you want multiple copies distributed in different places, you want be able to query your data even if some machines fail, or both.&quot;

One of the authors of the tests and blog post here, let me know if you have any questions about our testing process.

What is the difference between Rqlite adn Dqlite?

How people use SQLite outside single app, how do you manage RBAC?

EDIT: Title has been slightly changed, now. It was originally &quot;Jepsen testing of rqlite, the distributed DB built on Raft and SQLite&quot;<p>Hmm, perhaps a bit of confusion from the title. It sounds like they ran the Jepsen suite of tests against rqlite, which is great, but not done _by_ Jepsen &#x2F; Kyle (<a href="https:&#x2F;&#x2F;jepsen.io" rel="nofollow">https:&#x2F;&#x2F;jepsen.io</a>). Others have done this themselves too and that&#x27;s fine, but half the of the problem is correctly implementing the tests which has been done incorrectly by others in the past.