[dantiberian]

I don't really understand what this is offering beyond Cloudflare's recent release of running SQLite in durable objects: https://blog.cloudflare.com/sqlite-in-durable-objects/. Is it about providing an external interface to Cloudflare's SQLite databases?

[bhl]

The project is open source (https://github.com/Brayden/starbasedb/blob/main/src/index.ts). Yes to it provides a way to update Cloudflare's SQLite with HTTP.

[Horusiath]

If that's the case there's libsql (https://github.com/tursodatabase/libsql) which already provides HTTP clients, embedded replicas (essentially good old SQLite but with replication support), self-hosted SQLite server and is maintained by a company using it for their own product.

[brunoqc]

Some day I really need to learn when to use sqlite in a durable object vs the eventually consistent one (r2).

[MayorMonty]

iirc they are both powered by the same engine to stream and replicate the WAL. I believe R2 is now implemented as a Durable Object backed by SQLite now.

[brunoqc]

Does this mean that R2 is not "eventually consistent" anymore?

I wonder what are the use cases (and when it's safe) to use "eventually consistent".

I'm guessing that maybe things like social media posts could be fine with "eventually consistent". It's not really critical to have the latest data.

I'm guessing that things like a shopping cart, a user account, a session shouldn't use a "eventually consistent" database.

[brayden_wilmoth]

Still think there is a lot we can add to StarbaseDB to make the developer experience on SQLite databases better, and personally I think it starts with a better external interface. Provide a frictionless way to get started. Then figuring out how to improve developer experiences on how they interface with databases.

Is it auto-accessible REST endpoints? Easy to implement websocket support for the database? Data replication for scaling reads? Offline data syncing? A lot of potential wins for a layer like this to build on.