4 ms·
Author here. Cool to see the post make it up on HN again. I'm still as excited as ever about the SQLite space. So much great work going on from rqlite, cr-sqlit
by benbjohnson 3y ago
Author here. Cool to see the post make it up on HN again. I'm still as excited as ever about the SQLite space. So much great work going on from rqlite, cr-sqlite, & Turso, and we're still plugging away on LiteFS. I'm happy to answer any questions about the post.
- jjtheblunt 3y agoIs there a recommendable way to feign a graph database within SQLite? (because read only replication would be fantastic on fly.io for us.)
- benbjohnson 3y agoSQLite has very little per-query overhead (as opposed to a database connection over a network) so I would think you could traverse a graph using multiple small queries rather than using a graph query language.
- jjtheblunt 3y agoyep that's what i am doing
- rubenv 3y agoWhat's the status on litestream? Does that have a future as well or is it LiteFS all the way?
- benbjohnson 3y agoLitestream definitely has a future. Our goal is to keep it as a simple single-node disaster recovery tool though so it won't see as much feature development as something like LiteFS. We've been focused a lot on LiteFS & LiteFS Cloud to get them in a good place but I'm looking forward to going back and updating Litestream more regularly.
- rubenv 3y agoNot much feature development is perfectly fine if it works! Things don't have to evolve. Planning to use litestream as a library to dynamically swap in/out dozens of databases in a process. Looking at the code it'll easily allow that (super clean, kudos!). So many thanks, it's going to enable a lot of new things!
- otoolep 3y agoThanks Ben! rqlite[1] creator, happy to answer questions too. [1] https://www.rqlite.io https://www.rqlite.io