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?
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.
Some day I really need to learn when to use sqlite in a durable object vs the eventually consistent one (r2).
I find the website design to be quite charming. Actually evokes some of the Outer World game vibes.
How does this compare with Cloudflare’s new offering SQLite it durable objects: https://blog.cloudflare.com/sqlite-in-durable-objects
This 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...
+1. Love the cassette falling in place with the sound effect. Still don't know what it actually does though, but that is very satisfying.
Am I right to say that this is a template on top of cloudflare durable objects, not an actual software of its own?
This is awesome. We’ve adopted a similar architecture with DO. Does it do data sync across devices? Offline first? Or is it all online thru DO and D1?
DO = Cloudflare Durable Objects, https://developers.cloudflare.com/durable-objects/
D1 = Cloudflare D1, https://developers.cloudflare.com/d1/
Just incase someone else was as lost as me.
ah, DO always translates to Digital Ocean for me. So thanks for that! acronyms with name collisions are the woooorst
What is the difference between this and Cloudflare’s first party D1 database offering? https://developers.cloudflare.com/d1/
D1 is SQLite
It appears the blog links are broken. Are those also supposed to function as the documentation?
Same here. I wonder if it’s only broken for us or if it’s broken for everybody else as well.
This 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?
`Isolation. Due to the nature of our queue and query executions, everything is synchronous by nature so no two queries can be ran concurrently making them run in an isolated nature by default. Check.`
I'm not sure if I misunderstood something, but using a global queue/lock to enforce isolation properties seems to be just a little disingenuous for a dbms. It works, but it's odd to talk about isolation in a system with zero concurrency. It's like saying a bicycle gets infinite miles per gallon in fuel efficiency.
Cloudflare recently updated this:
Zero-latency SQLite storage in every Durable Object
This has the same name as an Elon Musk project. I can see the point of reusing names (this is a clever spin after all), but I’d expect the association to evoke quite some negative reactions.
Any comparison with Dzero?
ELI5: Does "Open source, scale-to-zero, HTTP SQLite database built on top of Cloudflare Durable Objects" mean that you should pay and/or use Cloudflare for this? Or CDOs are generally available outside Cloudflare?