A LevelUP compatible leaderless multi-master database with eventual consistency, using hyperbee + CRDT + HLC. Similarly CockroachDB achieves replication on top of RocksDB, but here it is a pure P2P **streaming** database, with zero central management. LevelDB compatibility allows to use Dynalite on top to achieve DynamoDB compatibility with sophisticated auto-updated secondary indexes, and fairly complex queries. Work on Dynalite is almost completed to remove HTTP server, to make this combination perfect for serverless.
In this version of multi-hyperbee the related peers are saved only in memory.
That means that if the device restarts there is no info for restoring the relationship.
Solution
Save the list of related peers as a manifest in store hyperbee (multi-hyperbee has local store, local diff and many remote diff replicas.
Save the name of this key in the Header (first block in hyperbee or any other hyper data structure)
Use this key to save/update the manifest every time the new peer is added/removed.
Discuss if this works for other multi-feed structures
pgmemk
commented
3 years ago
Problem
In this version of multi-hyperbee the related peers are saved only in memory. That means that if the device restarts there is no info for restoring the relationship.
Solution
storehyperbee (multi-hyperbee has localstore, localdiffand many remotediffreplicas.Discuss if this works for other multi-feed structures
https://github.com/datproject/comm-comm/issues/134