The Kappa architecture

Another strategy to deal with a set of single-writer append-only logs is the Kappa architecture. Its basic concept is that each user has a local database into which data from several single-writer logs are aggregated. Our JavaScript implementation is [kappa-core] plus an emerging set of modules for different types of views (roughly comparable to database tables in that they usually aggregate append-only data e.g. into key-value stores with support for conflict resolution primitives. This ecosystem is developent by different projects that are based around sets of Hypercores, e.g. Cabal and Mapeo and peermaps. Currently, there's ways being developed to nicely deal with these sets of hypercores, asking peers for interesting parts, and replicating those efficiently.