benbjohnson

6 ms·

1.
by benbjohnson 7mo ago
If you can have multiple writers to a single database then you'd need to look at something like cr-sqlite[1] that uses CRDT to figure out conflicts. If you're just replicating separate databases then you might be able to replicate
2.
by benbjohnson 7mo ago
Litestream author here. You can use the built-in file replication. It'll replicate all your database changes to another path on disk. I use it a lot for testing things out: https://litestream.io/guides/file/
3.
by benbjohnson 7mo ago
Litestream author here. Currently we're handling the "single writer" issue outside of Litestream. We have controls in our internal systems that make it work well. But yes, the lease PR is the direction we're looking at g
4.
by benbjohnson 9mo ago
Author here. It will cache pages in memory right now but it doesn't do disk-based caching currently. That's a good idea though and probably not too difficult to implement. Feel free to post a feature request as a GitHub issue on t
5.
by benbjohnson 9mo ago
The VFS is read only but it will continuously poll for new updates so if you have a writer somewhere else using regular Litestream then it will pick up those updates automatically.
6.
by benbjohnson 9mo ago
Author here. You can query the state of a table from an hour ago with Litestream VFS. It won't give you versioned tables in the sense that every time you update a row that it writes a new version in a table somewhere though.
7.
by benbjohnson 9mo ago
Author here. We've done some proof-of-concept work on creating distributed leases using S3. We have some use cases internally where we've considered adding write capabilities to the VFS but we haven't started any work on it y
8.
by benbjohnson 9mo ago
Author here. Litestream VFS will automatically poll for new back up data every second so it keeps itself up to date with any changes made by the original database. You don't need any additional code (Python or otherwise) to use the VFS
9.
by benbjohnson 9mo ago
It worked great! Thanks for your work on it.
10.
by benbjohnson 9mo ago
Author here. The VFS support right now is currently read only so it's useful for something more like a shared cache of data.
11.
by benbjohnson 9mo ago
Author here. Yes, Litestream v0.5.3 has been released with a new read-only VFS option: https://github.com/benbjohnson/litestream/releases/tag/v0.5....
12.
by benbjohnson 11mo ago
Litestream author here. Yes, that's correct. LTX was the biggest hurdle to get over and was impossible to switch over incrementally. The storage layer change brings a lot of benefits and enables a lot of future work that we're rea
13.
by benbjohnson 1y ago
The changes are still in progress. The blog post was just about future work that we're working on. However, we don't have plans to do failover with Litestream at the moment.
14.
by benbjohnson 1y ago
Litestream saves WAL segments to a given time granularity. By default, it ships off WAL changes every second so you should be able to restore to any given second in your history (within your retention period).
15.
by benbjohnson 1y ago
Backups & read replicas are the primary use cases. If you're interested in local-first, you can check out projects like cr-sqlite[1]. [1]: https://github.com/vlcn-io/cr-sqlite
16.
by benbjohnson 1y ago
We don't support plug-ins at the moment but there's several backends at the moment (S3, Azure Blob Storage, Google Cloud Storage, SFTP, etc)
17.
by benbjohnson 1y ago
Not all corruption is detectable. You could make a copy during a transaction where only a subset of the transactions saved pages are persisted but all branch & leaf pages are pointed to correctly. That would give you a state of the data
18.
by benbjohnson 2y ago
I haven't read that paper but it seems like it's fixing a different problem of Byzantine fault tolerance. Most consensus systems that are internal for an organization don't have the Byzantine issue so it simplifies the proble
19.
by benbjohnson 2y ago
Thanks so much for letting me know! It's always hard to tell when I put something out there if it just gets lost in the ether. I'm glad to hear it helped so many folks.
20.
by benbjohnson 2y ago
It's all done with d3 and JavaScript. The visualizations aren't deterministic so I ended up writing a shitty Raft implementation in JS. Overall it was a terrible approach because it was so time consuming but I made it work. You ca
21.
by benbjohnson 2y ago
Author here. I'm happy to answer any questions although this project was from 10+ years ago so I could be a little rusty. Over the years I've been trying to find better ways to do this kind of visualization but for other CS topics
22.
by benbjohnson 2y ago
IIRC he was given shares in the company. https://news.ycombinator.com/item?id=39629939
23.
by benbjohnson 2y ago
LiteFS author here. I don't disagree with any points in the article but perhaps a reframing could help. I previously wrote a tool called Litestream that would do disaster recovery for a single-node SQLite server and I still think it&#x
24.
by benbjohnson 3y ago
We have an region-aware S3 replacement that's in beta right now: https://community.fly.io/t/global-caching-object-storage-on-...
25.
by benbjohnson 3y ago
Do you mind if I ask who you work for? I’m in Denver as well and I’m always curious what companies are doing 4x8 or even 4x10.
26.
by benbjohnson 3y ago
Author here. The comparison was meant to be about how Postgres (or any client/server RDBMS) is typically deployed. Yes, you can deploy Postgres on the same machine but I wouldn't say it's common. Maybe I could have expanded m
27.
by benbjohnson 3y ago
SQLite 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.
28.
by benbjohnson 3y ago
Litestream 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
29.
by benbjohnson 3y ago
Author here. My goal in the comparison was only in terms of scope, not that Postgres folks should be penalized for having good documentation. I think Postgres is great and it makes sense to use it when it's called for. But I think it c
30.
by benbjohnson 3y ago
Author here. The single-node restriction for Litestream was one of the main reasons we started LiteFS. There isn't a way to handle streaming backup from multiple nodes with Litestream & S3 as SQLite is a single-writer system and th

More ›