3 ms·
SQLite is a remarkably good solution to most of these problems, if deployed correctly. For your main line-of-business database? Of course not. But a deployment
by samatman 5y ago
SQLite is a remarkably good solution to most of these problems, if deployed correctly.
For your main line-of-business database? Of course not. But a deployment of rqlite[0] for your service workers in a read-heavy workload? cuts out a round-trip out of the VM, mocking is trivial, there's a lot to like there.
[0]: https://github.com/rqlite/rqlite https://github.com/rqlite/rqlite
- eloff 5y agoYou're missing the whole point of the article. If you set this up in an active-active configuration (if that's even supported) you have the exact same distributed systems problems as the author.
- cortesoft 5y agoThe whole point of having a database is that you need persistent data that is consistent for all clients. You can’t have a bunch of SQLite dbs and get that.
- otoolep 5y agorqlite author here. Happy to answer any questions about it.