46 points ghostfoxgod 2 hours ago 6 comments

feverzsj 1 hour ago | parent

Sounds like you should use a database-per-user design.

mkesper 1 hour ago | parent

Right, then even sqlite should be enough?

CyrusGrissom 26 minutes ago | parent

I couldn't find the word "replication" in the post or on the GitHub page. So, what about fault tolerance?

tomasol 16 minutes ago | parent

I'm curious too. The only backup I found on GitHub uses cp; they may use filesystem snapshots or Litestream in production. If it’s Litestream, litestream sync -wait can force a sync after a write and wait for remote replication to complete.

bob1029 18 minutes ago | parent

> JSON blobs

An alternative to faster blob storage is to represent the blob's schema in SQL directly.

If most blob updates are incremental you can eliminate a significant amount of storage IO and garbage collection this way.

One SQLite database per blob type with a metadata SQLite db that tracks each. We could leverage powerful AI reasoning models to produce SQLite schemas and virtual table adapters for each encountered JSON schema type.

zodwick 9 minutes ago | parent

all roads lead to sqlite