3 ms·
SQLite uses serializable isolation by default, this is built on top of that. I'm also curious how Raft is used and what the resulting guarantees on distributed
by samatman 8y ago
SQLite uses serializable isolation by default, this is built on top of that.
I'm also curious how Raft is used and what the resulting guarantees on distributed table operations are, but I'm coming at it assuming good faith, since SQLite is... robust.
- atombender 8y agoExplained in the docs [1]. They replaced the SQLite WAL with one that uses Raft. Each actor has its own WAL, and so I suppose only operations within a single actor are consistent. Multi-actor transactions use two-phase commits. [1] http://www.actordb.com/docs-howitworks.html http://www.actordb.com/docs-howitworks.html
- thanatos_dem 8y ago> SQLite uses serializable isolation by default, this is built on top of that. That's sort of a meaningless statement tho. Everything in the world is built on top of RAM which is serializable. The real complexity comes in how those foundational blocks are abstracted and combined. We know that it's not performant at scale to represent an entire database log a single Raft group. So how are the Raft groups structured organized, and how and when do they cross-communicate?
- atombender 8y agoSee the docs [1]. As I understand it, each actor is a Raft group. Each actor has its own independent SQLite WAL. [1] http://www.actordb.com/docs-howitworks.htmlhttp://www.actordb.com/docs-howitworks.html http://www.actordb.com/docs-howitworks.htmlhttp://www.actord...