3 ms·
Some things that come to my mind: * no tuning (pg_hba, memory, WAL options etc etc.) * presumably fixed memory consumption (if similar to sqlite) * raft give
by uniqueuid 5y ago
Some things that come to my mind:
* no tuning (pg_hba, memory, WAL options etc etc.)
* presumably fixed memory consumption (if similar to sqlite)
* raft gives you usable failover out of the box, whereas with postgres, you need additional (and complex) solutions
* less operational complexity
- otoolep 5y agorqlite author here. Good summary, I generally agree. rqlite installation is also very easy, thanks to Go. Single, statically-linked binary you can just drop on your machine. rqlite also has a really simple build process (another explicit goal -- just execute 'go build') making it easy to build it yourself -- giving you a high-level of control over the actual software you run. https://github.com/rqlite/rqlite/blob/master/CONTRIBUTING.md#building-rqlite https://github.com/rqlite/rqlite/blob/master/CONTRIBUTING.md...