Good videos, with context.

Name the failure before choosing the mechanism

Distributed systems videos

Distributed systems videos are easier to compare when you name an observable failure: a process crashes, a message arrives late, or two machines disagree. Begin with how components communicate and recover, then examine how those behaviors can be tested.

Runtime mechanisms are not system-wide guarantees

Juric offers an entry through Erlang and Elixir’s approach to concurrent server systems. Wilson supplies a contrasting view through deterministic simulation. A supervisor restarting a process does not by itself tell you whether a request was completed exactly once. Trace a request across components and mark where information is lost or duplicated before deciding what recovery should mean.

Choose a starting point

Questions to take into the video

A successful scaling story is tied to a workload and an operational environment. Avoid turning one company’s architecture into a universal recipe.

Explore a connected subject

Databases & storage ↗Cloud, DevOps & reliability ↗
Sources and selection notes

By . Updated . We compared source-video titles, available uploader descriptions and the linked archive records. The choice of starting points and viewing questions is our editorial guidance. These notes do not claim full-video viewing or independent expert review.

The complete list below preserves the October 31, 2026 snapshot and its original score order. Its labels and summaries include AI-generated source material; topic membership is broader than our selected starting points. Availability and factual claims can change. Suggest a correction.

All 81 videos in this archive topic

Browse the full snapshot after choosing your starting point.