Topology
Concurrency
Consistency and Availability
- Lamport clock
- Vector clock
- System with vector clock
- Version vector
- System with version vector
- Dotted version vector
- Dotted version vector for optimistic replication
- Interval tree clock
- Time not timeout
- Raft
- Generalized Paxos
- Paxos: invariants
- Paxos: implement
- Paxos made live
- Paxos made practical
- Consensus: unlimited
- View-stamped replication (original)
- FLP
- CAPELC
- Snapshot
- Efficient failure detection
- Phi-accrual failure detector
- CRDT
- CRDT: JSON
- Replicated data consistency through baseball
- Robust replication
- 2-phase commit
- Cornus: efficient 2-phase commit
- Mergable persistent data-structures
- Operational transformation: collab-edit
- Chain replication
- CRAQ: chain replication
- Consistency-oriented SLA
- An ode to eventual consistency
- Session gurantees
- Consistency rationing
- Consistency tradeoff from consumer perspective
- Consistency violations in eventually-consistent systems
Scalability
- Consistent Hashing
- Chord
- A cooperative filesystem with DHT
- Beehive: O(1) DHT Lookup
- Kademlia
- Pastry
- Tapestry
- CAN
Systems
- Spanner
- GFS
- Hadoop
- Cassandra
- Configerator
- MapReduce
- Bigtable
- Sinfonia: distributed address space
- PNUTS
- Megastore
- Azure Storage
- Redshift
- CosmosDB
- Service Fabric
- Consistency levels in CosmosDB
- Firestore
- Aurora
- Coordination
- KVS
- P2P
- Blobstore
- CDN
- Streaming
- Tracing
- Unique ID
- Time-series DB
- Service discovery
- Monitoring
- Elastic search
- Lambda
- Control plane: principles
- Postmortem
- COE
- Caching
- Message Queue
- Rate limiter
unreasonably effective 
Leave a comment