Distributed Systems¶
Tanenbaum, A. S., Maarten van Steen, D. S. P., & Paradigms, 2. e. (2007). Distributed Systems: Principles and Paradigms. Pearson.
Cited by¶
6 citations across 6 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Bottleneck
This sourceBiblio reference (never cited in body).
- Concurrency
- The clarifying force is to make coordination requirements checkable and to turn implicit temporal assumptions into explicit guards
This sourceCanonical distributed-systems text covering synchronization, coordination, consistency, and replication. SUPPORTS marker 052 (clarity: turning implicit temporal assumptions into explicit guards) and marker 054 (independent agents overlapping in time without corrupting each other's work). DOI/link is the archive.org copy. NOTE: the embedded annotation in the source ('load balancing as distributing divisible work ... distribution vs provisioning') is a mismatched carry-over from another prime's use of this text; the book nonetheless supports the general coordination/clarity claims on 052/054.
- The clarifying force is to make coordination requirements checkable and to turn implicit temporal assumptions into explicit guards
- Idempotence
- .
This sourceChapters on messaging and at-least-once delivery establish idempotency in message-passing protocols.
- .
- Load Balancing
- Its essence is spreading demand over parallel resources according to a routing rule, exploiting the fact that aggregate capacity is only useful if demand can be steered toward wherever spare capacity currently exists.
This sourceCanonical distributed-systems textbook: develops load balancing as distributing divisible work across a pool of interchangeable units behind one logical endpoint, treating the pool as a single elastic resource and distinguishing distribution (shape of the load) from provisioning (its mean).
- Its essence is spreading demand over parallel resources according to a routing rule, exploiting the fact that aggregate capacity is only useful if demand can be steered toward wherever spare capacity currently exists.
- Scalability
- The architectural strategies that transform the bottleneck: replication, partitioning (sharding), caching, asynchronous processing, load balancing, or workflow restructuring
This sourceCanonical distributed-systems textbook: develops load balancing as distributing divisible work across a pool of interchangeable units behind one logical endpoint, treating the pool as a single elastic resource and distinguishing distribution (shape of the load) from provisioning (its mean).
- The architectural strategies that transform the bottleneck: replication, partitioning (sharding), caching, asynchronous processing, load balancing, or workflow restructuring
Domain-specific¶
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.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:5ff94f87dd3f · see in the full table