Distributed Content Hosting
A service for content providers, built on a content infrastructure
- for any of the network’s own customers with content to distribute
- no complaints; extends the relation between content provider and end user; pays for improved performance, resilience, reach of content distributed close to requests;
- simple to implement and manage
Requirements:
- well-engineered big network
- good management of IP address space
- content engines well-placed in network, running a routing daemon such as gated
- script-based tools for management
Routing does heavy lifting of getting requests to content collected in convenient places in network
Infrastructure forms basis of many new content services