Distributed Systems

Tanenbaum, A. S., & Steen, M. v. (2017). Distributed Systems. CreateSpace Independent Publishing.

Type

Book

Intellectual base

Review or monograph

Year

2017

Link

https://www.distributed-systems.net/index.php/books/ds3/

Cited from

computer_science, engineering_design

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).

• 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.

• 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.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:e6e32d573d22 · see in the full table