CDN

As explained in Server-Side WebAssembly

A content delivery network is a geographically distributed network of servers that caches and delivers content close to end users.

A content delivery network (CDN) distributes servers across many locations and delivers content from an edge node near the user. This reduces latency by shortening the physical distance to content and computation. section 9.2.3

CDNs support progressively richer delivery patterns:

• Cache static assets such as HTML, images, and scripts at locations worldwide. section 9.2.3
• Receive requests at edge nodes and perform lightweight processing, such as blocking bots or malicious traffic. section 9.2.3
• Run application logic at the edge, bringing dynamic features closer to users instead of sending every request to centralized infrastructure. section 9.2.3

A blog with comments

A static blog can serve readers in Tokyo from a nearby Tokyo edge location rather than an origin server in Virginia. A comment system can also run near the reader, fetching, ordering, nesting, and filtering comments without routing every request to a centralized database. section 9.2.3

Figure 9.4 Request flow with edge compute. Incoming requests first hit the edge node, where user-defined Wasm code can perform logic before routing to the centralized cloud backend.

Trace how a request reaches an edge node, where user-defined Wasm code can process it before routing to a centralized cloud backend. section 9.2.3

How Server-Side WebAssembly covers it

How deep it goes

Explains caching, request filtering, and edge execution through a blog example, stopping short of implementation details.

Examples

Uses a globally cached blog, a dynamic comment system, and a request-flow diagram.

What you can do after

Evaluate/understand how CDNs reduce latency and where edge computation fits alongside centralized backends.

How it connects

Connects CDNs with edge computing, centralized cloud backends, databases, and WebAssembly.

liveBookmanning.com

Read Server-Side WebAssembly on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Building Web APIs with ASP.NET CoreA content delivery network is a geographically distributed network of intermediary servers that delivers or caches content from locations closer to clients.
• 

  liveBookmanning.com
  Pro ASP.NET Core 7, Tenth EditionA content delivery network is a distributed service that delivers web assets from geographically or topologically proximate servers.
• 

  liveBookmanning.com
  LatencyA content delivery network is a geographically distributed network of servers that caches and delivers content from locations near users.

Compare how 4 books explain CDN →

Related concepts

• distributed file systemkind of · A distributed file system stores and manages files across multiple networked computers while presenting clients with a unified filesystem-like interface.
• static siteused by · A static site is a website primarily devoted to presenting content through fixed or prebuilt pages rather than pages dynamically generated for each request.
• meanaddresses · A mean is a measure of central tendency, calculated as the arithmetic average of values or, for a random variable, as the probability-weighted average of its possible values.
• cachinguses · Caching is the practice of storing reusable data or computation results so later access can avoid repeating retrieval or computation.
• replicationuses · Replication is the creation or maintenance of multiple copies of data, state, or functionality across separate locations or components.

This explainer was generated by Manning's knowledge graph from the text of Server-Side WebAssembly. The section links point to the parts of the book it draws on.