Starbase: SQLite on the Edge
21–30 of 49 posts
Re: Starbase: SQLite on the Edge
#22Re: Starbase: SQLite on the Edge
#23This is pretty cool. Great artwork too. Building edge DBs on top of S3 or R2 had interested me for a long time. Thanks for writing it! Update: bug in redirection: https://starbasedb.com/blog/blog/blog/blog/blog/blog/develop...
Re: Starbase: SQLite on the Edge
#24How does this compare with Cloudflare’s new offering SQLite it durable objects: https://blog.cloudflare.com/sqlite-in-durable-objects
Re: Starbase: SQLite on the Edge
#25I 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?
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.
Re: Starbase: SQLite on the Edge
#26Re: Starbase: SQLite on the Edge
#27I find the website design to be quite charming. Actually evokes some of the Outer World game vibes.
I have this old school expectation that I should be able to understand what your website/product/project is about but reading the first few sentences in the "above the fold" section of your homepage. I don't want to play a game or click below the fold "read more" links to try and find out what this web content has to do with the domain name "starbasedb".
Perhaps they actually know their intended (seemingly game developer?) audience that I give them credit for? But I do have plans (admittedly only very vague plans right now) to use one of the available "SQLite from javascript in a webpage querying the SQLite file in an object store like S3 without a web backend" techniques or projects. Maybe they'd work for me with my non game oriented use case? I don't know, it seems like they don't want me to find out...
Re: Starbase: SQLite on the Edge
#28This is very appealing. If the authors are reading: What is the architecture overview? Does each worker have a copy or do all of them work on the same DB files? How does it handle concurrent workers and db locking? Is SQLite native locking mechanism sufficient in this application?
We probably need to build out some sort of data replication to scale reads though Durable Objects are limited to 1000 RPS.
Re: Starbase: SQLite on the Edge
#29DO implements a very comprehensive strategy to mitigate data loss in DO backed by SQLite. But Starbase seems to add a layer of query caching on the application level, which seems to be naively implemented (I might be misunderstanding, please correct if I'm wrong).
[1] https://starbasedb.com/blog/developing-acid-transaction-supp...
Re: Starbase: SQLite on the Edge
#30From what I could understand of their architecture [1], you may lose data when the machine running DO fails. DO implements a very comprehensive strategy to mitigate data loss in DO backed by SQLite. But Starbase seems to add a layer of query caching on the application level, which seems to be naively implemented (I might be misunderstanding, please correct if I'm wrong). [1] https://starbasedb.com/blog/developing-aci…
Learn more about that here: https://github.com/Brayden/starbasedb/issues/12