Show HN: rqlite 7.15, the distributed DB built on SQLite, now with backups to S3
github.com
github.com
And I can't decide whether it's genius or madness at work.
I think there might be a huge potential if rqlite would also announce/discover other compatible nodes via dns-sd.
"Why would I use this, versus some other distributed database?
rqlite is very simple to deploy, run, and manage – in fact, simplicity-of-operation is a key design goal. It’s also lightweight and easy to query. It’s a single binary you can drop anywhere on a machine, and just start it, which makes it very convenient. It takes literally seconds to configure and form a cluster, which provides you with fault-tolerance and high-availability. With rqlite you have complete control over your database infrastructure, and the data it stores.
That said, it’s always possible it’s too simple for your needs."
[1]: https://rqlite.io/docs/faq/#why-would-i-use-this-versus-some...
Yes, you still need the data at every node. rqlite is not about edge-compute specifically (though many solutions have come along after rqlite was created to address that need, I guess I should have responded to that demand much earlier instead :-)). One of my primary goals with rqlite has always been ease-of-deployment and ease-of-use. I wanted to build a quality distributed database that was both really reliable and super easy-to-use.
Check out the FAQ, which might answer some more of your questions: https://rqlite.io/docs/faq/