Super interesting. A major point to be aware of from the docs:<p><pre><code> Note what this is not: a distributed SQL engine. [...]
SQLite on RADOS is meant to be accessed by a single SQLite client
database connection at a given time.
</code></pre>
So it distributes the backend storage across multiple nodes for the increased reliability, but any individual SQLite database is only accessible from a single node at a time.<p>That still sounds like a good trade off in a lot of cases.<p>Performance wise, the docs mention this when SQLite is configured for WAL journaling:<p><pre><code> You can expect around 150-250 transactions per second ...
</code></pre>
That's easily good enough for a lot of things. Obviously that would vary too depending on how the Ceph cluster itself is set up.<p>Wonder if this could be extended somehow, maybe with range locking?, to enable simultaneous operations from multiple nodes?
Thereby to create a cheap mans Oracle RAC equivalent... :)