Hacker News Reader

Comment by ncruces | Hacker News Reader

I mean, that's literally their "What’s next?" from the OP: https://fly.io/blog/litestream-v050-is-here/#whats-next

They already have a prototype, and... it's pretty rough on the edges.

I'm porting it to my Go SQLite driver and already ran into a bunch of issues. But it seems at least feasible to get it into a working shape.

https://github.com/benbjohnson/litestream/issues/772

https://github.com/ncruces/go-sqlite3/compare/main...litestr...

View on HN

Interesting! I really like your wasm compiled SQLite more than the pure Go one, so it is what I use most of the time.

What exactly are you trying to port?

A VFS that allows you to directly open a Litestream replication target (e.g. S3) as a read-only database and run queries against it without ever having to download the entire database (e.g. to an ephemeral instance that doesn't even have the disk space for it).

Interesting. Any plans for a cache? Or would that just be a litestream thing

I… honestly don't know. I saw the announcement some time ago (the revamped post) and started following their repo. They did mention caching to hide latency.

When I saw the v0.5.0 tag, I dived into just porting it. It's just over a couple hundred lines, and I have more experience with SQLite VFSes than most, so why not.

But it's still pretty shaky.

My version of the VFS should be ready for testing.

After some testing, I expect it to be working correctly in the vast majority of cases, but the performance may disappoint. The original still needs work.

https://github.com/ncruces/go-sqlite3/tree/litestream

Reply on news.ycombinator.com