kappa-core

Currently Beaker only has Web APIs for Hyperdrive, but we're going to add Hypercore APIs Hypercore is lower-level - it's basically an append-only log. There have been some projects that use it directly such as Kappa-core [1]. You might want it particularly for CRDT work, but generally I think you can use the filesystem to do pretty much anything, and that has the benefit of a regular data-form that can be explored using the terminal and files explorer and browser and etc. [1] https://github.com/kappa-db/kappa-core

I'm not deeply familiar with Syncthing but here are some differences based on what I do know: - Hyperdrive includes mass-publishing as a usecase, so it uses public-key URLs and a bandwidth-sharing mechanism among its active peers (like BitTorrent) - Hyperdrive is built on a general-purpose protocol called Hypercore which is a signed append-only log. These logs can be used for other datastructures. Some examples [1] [2] [1] Kappa-core, a general-purpose db built on the logs https://github.com/kappa-db/kappa-core [2] Cabal, a chat network https://cabal.chat/

Many projects[1][2][3][4] in the dat ecosystem use kappa-core[5] for multi-user applications on top of hypercores (the low-level append-only log used by dat). kappa-core is designed around the kappa architecture where the logs serve as the historical record and primary source of truth (so you get version control) and materialized views ingest the logs to answer application-specific queries. Some nice properties of the kappa-core implementation of this architecture are that: * works fully offline by default and many of the apps (especially mapeo) are designed for very offline use * device to device replication is first-class * you can completely rebuild the materialized views from the log data whenever your schema changes (very nice way of handling database migrations) * there's a lot of flexibility in how you design the materialized views