SQLite – The Session Extension

• rqlite

  112 14,862 9.9 Go

  The lightweight, distributed relational database built on SQLite.

  

This exists already with rqlite: https://github.com/rqlite/rqlite

As much as I love the idea, Raft is not a silver bullet and can break in strange and inconspicuous ways that may be difficult to fix. It can also lead to subtle inconsistencies in the data depending on what data you are putting in it. Overall it may be good in some situations, but I doubt it will dislodge Postgres in any meaningful way.

• dqlite

  33 3,716 9.5 C

  Embeddable, replicated and fault-tolerant SQL engine.

  

rqlite is nice but it's got limitations that made me look elsewhere. https://dqlite.io/ does it in C and allows for transactions and can be used for the Go sql.DB object.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• citus

  61 9,801 9.5 C

  Distributed PostgreSQL as an extension

  

I mean... why wait? SQLite + Paxos already exists: https://bedrockdb.com/

As a cherry on top, Postgres + Raft/Paxos already exists, too. It's called Citus: https://github.com/citusdata/citus

While I enjoy the spirit of your comment the meat of it is hand wavy. Many of the reasons people enjoy SQLite so much vanish the moment you introduce a consensus protocol or any sort of replication algorithm between online nodes. A better investment would be tooling and systems that guide us on how to operate multi-node stateful systems and inform of us of probabilities of bad things happening.

• Bedrock

  23 1,044 9.4 C

  Rock solid distributed database specializing in active/active automatic failover and WAN replication (by Expensify)

  

I mean... why wait? SQLite + Paxos already exists: https://bedrockdb.com/

As a cherry on top, Postgres + Raft/Paxos already exists, too. It's called Citus: https://github.com/citusdata/citus

While I enjoy the spirit of your comment the meat of it is hand wavy. Many of the reasons people enjoy SQLite so much vanish the moment you introduce a consensus protocol or any sort of replication algorithm between online nodes. A better investment would be tooling and systems that guide us on how to operate multi-node stateful systems and inform of us of probabilities of bad things happening.

Suggest a related project