upvote
rqlite[1] author here, happy to answer any questions.

[1] https://rqlite.io

reply
An honor to see you here. I used rqlite for a project i want to be available globally, in a small package i can myself manage, without having to bother with clustering postgres. I appreciate the ease of implementation in code, and how easy it is to manage operationally.
reply
Great to hear, ease of operations is one of the main design goals. I've too many scars from running complicated systems. Of course that means that the rqlite feature set has remained focused (a nice way of saying "limited"), but in exchange, if it matches your use case, it can work well.
reply
> Horizontally scalable, distributed.

This doesn't describe rqlite, at least.

reply
(Hi Phil!)

Correct, I read the post. Agreed, rqlite is not a great fit for high-throughput durable writes since all writes go through the Raft Leader. This is not specific to rqlite -- all systems which put Raft in the data plane[1] have the same challenge.

rqlite does offer a Queued Writes mode[2], which allows you to trade durability for much greater write throughput. The post mentions something similar -- async_write -- but their post claims they also make the data queryable before it is durable, unlike rqlite.

[1] https://youtu.be/8XbxQ1Epi5w?t=2306

[2] https://rqlite.io/docs/api/queued-writes/

reply
One detail: if you batch up your writes in the client, and send that batch through a Raft-based data plane system, you can get high throughput. But then you are paying with latency, as the clients have to wait until they have a batch worth of data before making the write request to the Raft-based system. rqlite calls this approach Bulk Requests[1].

[1] https://rqlite.io/docs/api/bulk-api/

reply