- Dynamo: Amazon’s highly available key-value store
- Harvest, yield, and scalable tolerant systems
- Lessons from giant-scale services
- Delta State Replicated Data Types
- The Swarm Protocol 1.2.1
- A Comprehensive Study of Convergent and Commutative Replicated Data Types
- A Commutative Replicated Data Type For Cooperative Editing
- CRDTs: Consistency without concurrency control
- Borrowing an Identity for a Distributed Counter
- Formal Design and Verification of Operational Transformation Algorithms for Copies Convergence
- Highly Available Transactions: Virtues and Limitations
- Time, Clocks and the Ordering of Events in a Distributed System
- Synchronizing Clocks in the Presence of Faults
- Implementing a Register in a Dynamic Distributed System
- Dotted Version Vectors: Logical Clocks for Optimistic Replication
- The Byzantine Generals Problem
- Extending Eventually Consistent Cloud Databases for Enforcing Numeric Invariants
- Consistency in Non-Transactional Distributed Storage Systems
- Survey on consistency conditions
- Linearizability. A Correctness Condition for Concurrent Objects
- Brewer’s conjecture and the feasibility of consistent, available, partition-tolerant web services
- Perspectives on the CAP Theorem
- CAP Twelve Years Later. How the "Rules" Have Changed
- Spanner, TrueTime & The CAP Theorem
- Chain Replication metadata management
- Spanner: Google’s Globally-Distributed Database
- A Critique of the CAP Theorem
- Fallacies of distributed computing
- Two Generals' Problem
- Byzantine fault tolerance
- Vector clock
- Lamport timestamps
- Matrix clock
- Version vector
- Conflict-free replicated data type
- Linearizability
- You Can’t Sacrifice Partition Tolerance
- Notes on Distributed Systems for Young Bloods
- Why Logical Clocks are Easy
- Why Vector Clocks are Easy
- Why Vector Clocks are Hard
- Vector Clocks Revisited
- Vector Clocks Revisited Part 2: Dotted Version Vectors
- Version Vectors are not Vector Clocks
- Causal Context
- Why Cassandra doesn’t need vector clocks
- The network is reliable
- The CAP FAQ
- Problems with CAP, and Yahoo’s little known NoSQL system
- CAP, Availability, High-Availability and Big Data databases in a world of partitions
- Hermitage: Testing the "I" in ACID
- Linearizability versus Serializability
- CAP Twelve Years Later: How the "Rules" Have Changed
- Introduction to Reliable and Secure Distributed Programming
- Designing Data-Intensive Applications
- Distributed Systems
- ZooKeeper. Distributed Process Coordination
- The Final Causal Frontier
- Consistency without consensus in production systems
- Distributed, Eventually Consistent Computations
- CRDTs Illustrated
- CRDTs in Practice
- CRDT: Datatype for the Apocalypse
- Eventually Consistent Data Structures
- Strong Eventual Consistency and Conflict-free Replicated Data Types
- The New Redis Database Built on CRDT Approach
- Distributed Systems 101
- Prototype implementation of Lasp in Erlang
- Akka Distributed Data
- Swarm - reactive data sync middleware
- Data synchronization for all mobile apps
- JavaScript replicated model (M of MVC) library
- An example Swarm+React project
- Official React bindings for Swarm.js
- SwarmDB Example Chat Application
- SwarmDB Example Mice Application
- SwarmDB Example TodoMVC Application
- Riak Ruby Client
- The Riak client for Ruby
- Riak Ruby libraries
- Docker image for running a minimal Riak KV cluster