Distributed Systems¶
Tanenbaum, A. S., & van Steen, M. (2017). Distributed Systems. CreateSpace Independent Publishing.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Client Server Model
- The single coordination surface between the two sides is the request/response protocol, which is the only place the otherwise-independent clients and server must agree.
This sourceStandard text defining the client–server architectural model, request/response coordination, and its canonical instances (web, DNS, databases, email).
- The single coordination surface between the two sides is the request/response protocol, which is the only place the otherwise-independent clients and server must agree.
- Compatibility
- A software library can be backward-compatible (old code runs unchanged) without being forward-compatible (new code may break on older versions), a distinction Tanenbaum and Van Steen (2017) develop in their canonical treatment of openness in distributed systems.
This sourceCanonical distributed-systems textbook: under "openness" it defines interoperability and portability and treats compatibility (whether components built to the same interfaces can substitute and coexist) as a condition distinct from active coordinated interaction, the basis for the backward/forward-compatibility distinction.
- A software library can be backward-compatible (old code runs unchanged) without being forward-compatible (new code may break on older versions), a distinction Tanenbaum and Van Steen (2017) develop in their canonical treatment of openness in distributed systems.
- Consistency Model
- Distributed computing. Linearizability, sequential consistency, causal consistency, eventual consistency, and snapshot isolation are named models for replicated databases, file systems, and caches
This sourceSurveys consistency models — sequential, causal, eventual — for replicated data stores, file systems, and caches.
- Distributed computing. Linearizability, sequential consistency, causal consistency, eventual consistency, and snapshot isolation are named models for replicated databases, file systems, and caches
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:e6e32d573d22 · see in the full table