CRDT: Garbage Collection · Issue #2 · ipfs-inactive/dynamic-data-and-capabilities
Problem: operation-based CRDTs work by nodes storing and forwarding operations to other nodes, in an append-only ever growing graph of operations. This has a few draw-backs: Storage space Slow star...
CRDT: Garbage Collection · Issue #2 · ipfs-inactive/dynamic-data-and-capabilities · GitHub Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} Uh oh! There was an error while loading. Please reload this page . This repository was archived by the owner on Apr 16, 2020. It is now read-only. ipfs-inactive / dynamic-data-and-capabilities Public archive Notifications You must be sign
Explore this link on the map →related reading
- Building a BFT JSON CRDTjzhao.xyz
- An Interactive Intro to CRDTs | jakelazaroff.comjakelazaroff.com
- CRDTs go brrrjosephg.com
- CRDT optimizationsbartoszsypytkowski.com
- About CRDTs • Conflict-free Replicated Data Typescrdt.tech
- Conflict-free replicated data type - Wikipediaen.wikipedia.org
- Data Laced with History: Causal Trees & Operational CRDTs — Archagon Was Herearchagon.net
- CRDT optimizationsbartoszsypytkowski.com
- Peritext: A CRDT for Rich-Text Collaborationinkandswitch.com
- GitHub - jackyzha0/bft-json-crdt: 🏰 the first JSON-like Byzantine Fault Tolerant CRDT · GitHubgithub.com
- Rhizome Research Logjzhao.xyz
- GitHub - josephg/diamond-types: The world's fastest CRDT. WIP. · GitHubgithub.com