dqlite

I feel like there should be a comparison table listing all of these engines and how they compare on their external dependencies, whether a single leader/any node can write, their shape (embeddable library vs server), etc. IMHO support for transactions is a pretty important dividing line. Some engines support full SQLite transactions while others - like rqlite - don't officially support BEGIN/COMMIT [0], which matters if you rely on multi-statement transactions. A friend/colleague has been building a pure-Python client for dqlite [1] (DB-API and SQLAlchemy), which may interest folks here. dqlite has full support for transactions, and like rqlite doesn't have external dependencies (ie no S3/Consul). No knock on rqlite or any other engine - dqlite has warts too [2]. [0] https://rqlite.io/docs/faq/#does-rqlite-support-transactions [1] https:/

Have you tried https://github.com/canonical/dqlite/pull/909 ?

Loads of '500 database locked' errors. https://github.com/canonical/dqlite/issues/908

I've had success in a production capacity with using rqlite before. There are also a bunch of other alternatives that still seem to be actively maintained, although I've only used rqlite myself before: - https://github.com/canonical/dqlite - https://github.com/rqlite/rqlite - https://github.com/Expensify/Bedrock

Just to point out, there are now SQLite replication and various "distributed database" projects which seem to work fairly well. They're probably not as battle tested as the PostgreSQL ones, but they are around, have users, and are actively developed. The ones I remember off the top of my head: * https://litestream.io * https://github.com/rqlite/rqlite <-- more of a "distributed database using RAFT" type of thing * https://github.com/canonical/dqlite

I'd be curious for a similar tuning with Dqlite: https://github.com/canonical/dqlite

For folks' context, the new tool that's being discussed in the thread mentioned by the parent here is litefs [0], as well as which you can also look at rqlite [1] and dqlite [2], which all provide different trade-offs (e.g. rqlite is 'more strongly consistent' than litefs). [0]: https://github.com/superfly/litefs [1]: https://github.com/rqlite/rqlite [2]: https://github.com/canonical/dqlite

I presume you're familiar with https://github.com/canonical/dqlite (made by my employer) and https://github.com/rqlite/rqlite (unrelated)? How will mvsqlite compare to those?

How about dqlite? https://github.com/canonical/dqlite

https://github.com/rqlite/rqlite https://github.com/canonical/dqlite

There already exists some distributed SQLite: https://github.com/canonical/dqlite https://github.com/rqlite/rqlite https://github.com/Expensify/Bedrock https://datacadamia.com/dit/kafka/connector/sqlite_distribut...

Postgres is better in the I-need-concurrency case -- I think it's the greatest RDBMS that's ever been made and would like someone to prove me wrong some day. SQLite's amazing too though, when you don't need concurrency (and most websites don't really -- especially the ones that should be scaling vertically instead of horizontally). Anyway here's some cool SQLite stuff: - https://github.com/CanonicalLtd/dqlite - https://github.com/rqlite/rqlite - https://datasette.readthedocs.io/en/stable/ - https://www.sqlite.org/rtree.html - https://github.com/sqlcipher/sqlcipher - https://github.com/benbjohnson/litestream - https://github.com/aergoio/aergolite - https://sqlite.org/lang_with.html#rcex3 - https://github.com/sql-js/sql.js - https://www.gaia-gis.it/fossil/libspatialite/index - https://github.com/h3rald/litestore - https://github.com/adamlou

A nice fix for this might be to extract just the wire protocol from dqlite to make a network connected, but not Raft replicated, sqlite. https://github.com/canonical/dqlite

So it looks like you can now distribute SQLite at the: Stmt level: https://github.com/rqlite/rqlite VFS Level: https://github.com/canonical/dqlite Block Level: https://github.com/benbjohnson/litestream Really cool enhancements to an awesome project!