Answers are grounded in this paper and cite their sources.
We deduce key design features behind the YouTube video delivery system by building a distributed active measurement infrastructure, and collecting and analyzing a large volume of video playback logs, DNS mappings and latency data. We find that the design of YouTube video delivery system consists of three major components: a “flat” video id space, multiple DNS namespaces reflecting a multi-layered logical organization of video servers, and a 3-tier physical cache hierarchy. We also uncover that YouTube employs a set of sophisticated mechanisms to handle video delivery dynamics such as cache misses and load sharing among its distributed cache locations and data centers.
No takes yet. Share an insight, caveat, or question.
Adhikari et al. (2012) studied this question.
Synapse has enriched 6 closely related papers on similar clinical questions. Consider them for comparative context: