"rqlite is very simple to deploy, run, and manage. It's lightweight. It's a single binary you can drop anywhere on a machine, and just start it. This makes it very convenient. It takes literally seconds to configure and form a cluster. 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."
https://github.com/rqlite/rqlite/blob/master/DOC/FAQ.md#why-...
Using the application to send the time, although not idea could be used as a workaround, but attempting to use non-deterministic functions in triggers becomes a lot harder.
1. https://github.com/rqlite/rqlite#limitations 2. https://www.sqlite.org/deterministic.html
* 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
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...