> What if we could run Postgres as a single file, and take advantage of the best SQLite has to offer?
Today I am announcing pg-micro, a crazy experiment I've been undertaking to make this happen.
pg-micro is different from other approaches because it is fully local, and expected to be fast: there is no concurrency limitation and no statement translation.
Really interesting design — especially using SQLite-compatible storage with a PostgreSQL interface.
I'm working on SNKV, which explores a different approach:
skipping the SQL layer entirely and focusing on a simple key-value interface.
It works closer to the storage layer (b-tree / WAL / pager concepts), aiming for a lightweight and minimal design, while supporting multi-process access.
Curious how you think about the tradeoff between SQL flexibility and a simpler KV interface.
3 comments
[ 2.5 ms ] story [ 22.4 ms ] thread> What if we could run Postgres as a single file, and take advantage of the best SQLite has to offer?
Today I am announcing pg-micro, a crazy experiment I've been undertaking to make this happen.
pg-micro is different from other approaches because it is fully local, and expected to be fast: there is no concurrency limitation and no statement translation.
[...]
https://x.com/glcst/status/2037254698898432278
I'm working on SNKV, which explores a different approach: skipping the SQL layer entirely and focusing on a simple key-value interface.
It works closer to the storage layer (b-tree / WAL / pager concepts), aiming for a lightweight and minimal design, while supporting multi-process access.
Curious how you think about the tradeoff between SQL flexibility and a simpler KV interface.
https://github.com/hash-anu/snkv