SEARCH LAVACS

Find a topic across LavaCS

Search textbooks, study guides, six encyclopedias, experiments and comparisons.

50 results · page 2 of 3

Distributed Systems · Study guides

Consensus, Raft, CAP, and Sharding

Trace majority replication and partition behavior, then distinguish consensus from sharding and replication.

Intermediate

Distributed Systems · Study guides

Trace logical clocks and causality

Assign Lamport labels to a three-process history and distinguish causal order, the failed converse, tie-breaking and elapsed time.

Intermediate

Distributed Systems · Study guides

Trace partitioning and live rebalancing

Move a range from three owners to four while separating mapping, copy, catch-up, authority cutover and old-copy cleanup.

Intermediate

Distributed Systems · Study guides

Quorum intersection and fault tolerance

Enumerate five-member read/write sets and separate overlap arithmetic from version selection, durability, partitions and membership changes.

Intermediate

Distributed Systems · Study guides

Reason about stream time and late events

Trace windows, watermarks, lateness, correction and replay for one sales history, separating progress from complete arrival.

Intermediate

Distributed Systems · Design patterns and optimization

Bounded queues and backpressure: control the waiting work

Make waiting, rejection, and load reduction explicit when arrivals exceed processing capacity. Work through concrete cases and separate mathematical assumptions from implementation checks.

Intermediate

Distributed Systems · Design patterns and optimization

Isolate resource occupancy with bulkheads

Compare a shared pool with reserved dependency pools, tracing stalled work, idle capacity, parent waits and release paths.

Intermediate

Distributed Systems · Design patterns and optimization

Trace circuit-breaker suppression and recovery

Trace closed, open and half-open states while separating failure windows, bounded probes, local refusals and fallback semantics.

Intermediate

Distributed Systems · Design patterns and optimization

Limit placement changes with consistent hashing

Insert a ring point and distinguish virtual points, capacity weighting, replica selection, configuration generations and live migration.

Intermediate

Distributed Systems · Design patterns and optimization

Propagate remaining request time

Allocate a 300 ms end-to-end budget across services and distinguish clocks, retries, cancellation and already committed effects.

Intermediate

Distributed Systems · Design patterns and optimization

Reconstruct state from authoritative event history

Use deposits, withdrawals and snapshots to reason about deterministic replay, concurrent append, event evolution, corrections and external effects.

Intermediate

Distributed Systems · Design patterns and optimization

Exponential backoff and jitter: avoid amplifying overload

Combine capped waiting, randomization, an overall deadline, and a contract for retryable operations. Work through concrete cases and separate mathematical assumptions from implementation checks.

Intermediate

Distributed Systems · Design patterns and optimization

Shed load to protect useful completion

Use concurrency, bounded queues, deadlines and priorities to reject excess work while preserving result semantics and recovery.

Intermediate

Distributed Systems · Design patterns and optimization

Choose owners with rendezvous hashing

Rank key-node scores and distinguish addition, removal, ties, replication, weighting and lookup cost.

Intermediate

Distributed Systems · Design patterns and optimization

Bound additional load with a retry budget

Use original requests, extra-attempt allowances and multilayer amplification to distinguish count limits, retry timing and idempotency.

Intermediate

Distributed Systems · Design patterns and optimization

Design saga compensation and unresolved states

Trace reservation, payment and cancellation to specify compensation retries, unknown outcomes, local invariants and recovery ownership.

Intermediate

Distributed Systems · Design patterns and optimization

Commit received identity and effect with an inbox

Commit received identity with its business update, then reason about concurrency, payload conflicts, retention and projection rebuild scope.

Intermediate