4 ms·
After looking through the repo, I'm still not sure exactly why you would want / need this. What exactly is the use-case here?
by notamy 9y ago
After looking through the repo, I'm still not sure exactly why you would want / need this. What exactly is the use-case here?
- free-ekanayaka 9y agoIf your application is: 1) Distributed (e.g. n equal processes running on n machines) 2) Needs some shared state across nodes 3) Would like that state to have SQL semantics (relations, transactions, etc.) 4) Not to heavy on writes to this shared state (I might provide some ballpark numbers at some point) 5) Wants to avoid the operational overhead of an external storage system (mysql, postgresql) 6) Wants to be fault-tolerant and have transparent failovers then dqlite might be a good choice.
- notamy 9y agoInteresting. Thank you for the explanation!
- hamandcheese 9y agoI would imagine it would be used similarly to etcd, zookeeper, consul, etc. as a distributed configuration store, with the advantage of being SQL and the schema goodness that comes along with that.