The read only bit is definitely a relatively simple afair. My Go driver supports it, through a combination of a VFS that can take any io.ReaderAt, and somethin

The read only bit is definitely a relatively simple afair. My Go driver supports it, through a combination of a VFS that can take any io.ReaderAt, and something that implements a io.ReaderAt with http Range requests (possibly with some caching). https://github.com/ncruces/go-sqlite3/blob/main/vfs/readervfs/example_test.go https://github.com/ncruces/go-sqlite3/blob/main/vfs/readervf... This is compatible with S3, but also GCS, and really any thing that supports http Range for GET. I've wanted to implement something writeable with concurrency. Not that it'll be great, but because people tend to do worse anyway (like run SQLite on top of something like GCS FUSE, and we can definitely do better than that), so why not? I've also worked with GCS concurrency features and locks, so I'd like to try and do better. But it's hard to be compatible with multiple cloud providers. So thanks for that!