But it has been tweeted about by the creator who works there so maybe it's not all that suspicious.
Was this vibecoded? Right down to the curl pipe? It's really strange that the code isn't public yet.
Yes, TigerFS works well with local PG - in fact, all of my testing framework uses this setup.
Big upside of this is latency; main downside is that such a deployment is primarily "single user mode."
One very interesting approach of this is ability to transparently share state / collaborate across machines, with these transactionally serialized at the common database.
I primarily work with Postgres, including both at scale and in very ephemeral environments. So just haven't looked at all what doing with this SQLite would mean.
I wonder what the performance characteristics are?
I'm assuming this is going to work well for small datasets that fit in memory, and probably less well beyond that. So good for config, context etc.
Also curious how the tables and index are maintained, for example if there's a write heavy workload. Does TigerFS handle rebuilding/repacking and the associated drudgery?
