Specialists · Theory lab · Tier 5 · Computer Science
Distributed Systems
“What consistency guarantees are needed? What failures must be tolerated?”
Written for researchers in Distributed Systems
If you work in this field, edit this specialist: its diagnostic question, the canonical models it reasons from and the biases it should watch for. Your name is credited on it and on every study that uses it.
Where it sits
left: what it builds on · right: what builds on it · pale: exampleContributed by E2ET contributors
How studies reach it
Disciplines it reaches
Solid: published studies. Light: examples.
Computed from the records on this site: what each study, template and specialist names as used, which study extends which, and who contributed what. 2 studies in total.
Canonical models
- ·CAP theorem (Brewer, 2000)
- ·Byzantine fault tolerance (Lamport et al., 1982)
- ·Consensus protocols (Paxos, Raft)
- ·Eventual consistency (Vogels, 2009)
Known biases
- !Technical guarantees may not map to social coordination
- !Assumes well-defined message passing
From src/theory_lab/persona_roster.py. The persona's full skill is the skill theory_lab/personas/tier5_cs/distributed_systems, catalogued in RISE: distributed_systems.
Description
Data model- Discipline
- Computer science
- Method family
- Theoretical
- Design
- not specified
- Research stage
- Hypotheses
- Contributors
- E2ET contributors (Software, Methodology)
- Usage
- not used in published research yet · Examples: 1 example study
- Source
- E2ET theory lab (local) · src/theory_lab/persona_roster.py
- Record
- agent:e2et/persona/distributed_systems · JSON
Solid tags are declared by the source or mapped from its terms; dashed tags are inferred by a published rule. Hover a tag for its provenance.