libsqlfs VS sqlite-zstd

Closest I found: https://github.com/guardianproject/libsqlfs

> The libsqlfs library implements a POSIX style file system on top of an SQLite database. It allows applications to have access to a full read/write file system in a single file, complete with its own file hierarchy and name space. This is useful for applications which needs structured storage, such as embedding documents within documents, or management of configuration data or preferences. Libsqlfs can be used as an shared library, or it can be built as a FUSE (Linux File System in User Space) module to allow a libsqlfs database to be accessed via OS level file system interfaces by normal applications.

- Use clone file to duplicate the cached data directory to give to individual tests.

One thing I'd like to pursue is to store the Postgres data dir in SQLite [1]. Then, I can reset the "file system" using SQL after each test instead of copying the entire datadir.

[1]: https://github.com/guardianproject/libsqlfs

Not sure about compression but somebody could probably hack it in an afternoon using this:

https://github.com/guardianproject/libsqlfs

or something similar to check the potential for speed up.

Maybe there isn't a database engine that explicitly supports file system daya structures, but you could implement a filesystem in the application layer using SQLite as a storage mechanism.

Here's an example of someone doing that very thing.

https://github.com/guardianproject/libsqlfs

now let's see what it takes to make absurd-fs, where we use https://github.com/guardianproject/libsqlfs to make a filesystem on top of sqlite on top of the File System Access API.

gotta keep ourselves fully looped. ⥀

Personally, 10GB. It's a database of all "person pages" on English Wikipedia with some extracted text (infobox and sections) compressed using sqlite-zstd[1]. About 350k rows.

(I know this is "small" compared to what SQLite can handle, but it's the biggest I've worked with. Most of my SQLite databases are under 500MB).

[1]: https://github.com/phiresky/sqlite-zstd

Have you compared LZ4 to other compression algorithms, zstd for example? ( https://github.com/phiresky/sqlite-zstd )

Given that LiteFS operates at the filesystem layer via FUSE, have you considered it against designs that use built-in features native to some filesystems? For example, I've considered a similar system design based on a single ZFS primary node that streams ZFS snapshots to reader nodes. With some coordination service (e.g. consul) it could still allow for the whole node promotion process.

There's library to compress sqlite databases with extensions like sqlite-zstd.