img
Home > Candidate Patterns > Content Distribution Network

Content Distribution Network

img

How can geographically distributed service consumers achieve equal access to service capabilities?

Problem

Service consumers deployed in different geographical locations can experience differences in latency, network availability, and bandwidth consumption when accessing a centralized service.

Solution

Include one or more local redundant implementations of the service nearby each service consumer, thereby allowing a given service consumer to interact with a deployed service within closer geographic proximity.

Application

Content distribution networks usually rely on the domain name system (DNS) to resolve logical service names in resource identifiers to the Internet Protocol (IP) address of the nearest redundant service implementation.

Impacts

Service capabilities that do not require immediate consistent updates between sites are able to be executed locally. This technique reduces consumer latency and bandwidth, and improves scalability by distributing service processing across sites.

The Brewer CAP theorem limits the ability for geographically separate sites to simultaneously support high availability, database consistency, and tolerance of network failures.

Architecture

Inventory, Composition, Service

Status

Under Review

Contributors

Raj Balasubramanian, Benjamin Carlyle, Cesare Pautasso
img

Services are redundant deployed as per consumer’s geographical location to build a Content Distribution Network.

Related Patterns in This Catalog

Response Caching

Related Service-Oriented Computing Goals

Increased Organizational Agility, Reduced IT Burden