https://engineering.fb.com/2021/08/06/core-infra/zippydb/
this is just a sharding algorithm, to start with
i just don't know what you are talking about, i'm talking about a local, key value store, on a single system, running with a flat-latency SSD data storage device behind it, like rocksdb
zippy just adds a centralised sharding algorithm to enable it to be more highly available
they don't fix the indexing problem that badger does
I'm talking about a KV store that is distributed. FoundationDB uses the SQLite btree code, or their own own btree based storage engine on each node for local storage. here's a talk about it while it was still in development: https://www.youtube.com/watch?v=5iqKu1pVDvE
that's my point, you talk about distributed, then it's not about the storage tech on the device, and there is no other than badger that makes indexing as cheap and fast
also, don't pollute my feed with apple tech bullshit
apple haven't done anything new since Lisa
also, i will be adding a full FTS to the eventstore i have been working on, it's my next priority for it, i'd be building that already...
i don't know what more really needs to be done to improve the functionality of data stores for #nostr - i think further advances would have to involve different types of data than kind 0 and 1s
