CDN
A content delivery network is a geographically distributed network of servers that caches or delivers digital content from locations near requesting users.
Building Web APIs with ASP.NET Core
A content delivery network is a geographically distributed network of intermediary servers that delivers or caches content from locations closer to clients.
- How it is used
- Places a CDN between clients and a production board-game API for intermediate caching and security.
- How deep it goes
- Defines the CDN and explains deployment trade-offs and common protections, without detailing a provider’s complete configuration sequence.
- Examples
- Uses a CDN-hosted board-game website and an architecture diagram placing CDN and reverse-proxy layers before its API.
- What you can do after
- Evaluate/understand whether CDN caching and security benefits justify an intermediate layer for an API deployment.
Pro ASP.NET Core 7, Tenth Edition
A content delivery network is a distributed service that delivers web assets from geographically or topologically proximate servers.
- How it is used
- Uses CDN URLs for JavaScript and CSS assets while configuring local files for CDN failures.
- How deep it goes
- Works through tag-helper attributes and generated HTML for two fallback tests; does not cover deploying a CDN.
- Examples
- Configures CDNJS jQuery 3.6.0 with a local script and CDNJS Bootstrap 5.2.3 with a computed-style-tested local stylesheet.
- What you can do after
- Operate/configure it by adding CDN URLs and local fallbacks to Razor layouts, then inspecting generated HTML to check the tests.
Acing the Frontend Interview
A content delivery network is a distributed network of servers that caches and delivers web content near end users.
- How it is used
- Uses edge caching to reduce user latency and backend pressure in distributed system design.
- How deep it goes
- Explains edge distribution, cacheable content, headers, invalidation, and multi-tier placement, but does not detail CDN internals.
- Examples
- Uses images, scripts, generated image thumbnails, HTTP headers, Cloudflare, and CloudFront as CDN examples.
- What you can do after
- Configure CDN caching with HTTP headers and reason about expiration, purging, latency, backend load, and complexity.
Latency
A content delivery network is a geographically distributed network of servers that caches and delivers content from locations near users.
- How it is used
- Reduces user latency and improves availability by moving replicated content toward geographically distributed users.
- How deep it goes
- Explains geographic placement, replication benefits, and consistency trade-offs without detailing cache invalidation or provider configuration.
- Examples
- Uses Tokyo-to-Virginia access, nearby Cloudflare data centers, and geographically replicated content as concrete examples.
- What you can do after
- Evaluate CDN placement by balancing proximity, latency, availability, replication, and consistency requirements.
Fundamentals of Cybersecurity
A content delivery network is a distributed system of geographically positioned servers that delivers digital content from locations near users.
- How it is used
- Speeds webpage delivery by serving requests from nearby regional locations instead of one central server.
- How deep it goes
- Defines regional delivery locations and cloud-hosted infrastructure, but does not detail CDN configuration or operation.
- Examples
- Compares CDN locations to regional warehouses and local distribution centers.
- What you can do after
- Understand why regional delivery locations can make webpages arrive faster around the world.
Server-Side WebAssembly
A content delivery network is a geographically distributed network of servers that caches and delivers content close to end users.
- How it is used
- Delivers static content and increasingly dynamic application logic from infrastructure positioned near end users.
- 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.
Also covered in
- The Well-Grounded Python Developer: How the pros use Python and Flask
- Go in Practice, Second Edition
- Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
- WordPress Power Toolkit: Harness AI to build next-level websites
- Modern Angular
- AI Agents for Offensive SecurityIn early access (MEAP)
What to know first
- load balancingLoad balancing is the distribution or adjustment of work across multiple resources to manage demand and reduce overload or imbalance.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
- cachingCaching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
- CSSCSS (Cascading Style Sheets) is a stylesheet language for specifying the presentation and layout of structured documents.
Related concepts
- 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.
- 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.
- cachinguses · Caching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
- meanaddresses · The mean is a measure of central location equal to the arithmetic average of numerical observations, or the probability-weighted average of a random variable’s possible values.
- replicationuses · Replication is the creation or maintenance of multiple copies of data, state, or functionality across distinct systems, nodes, or locations.
Questions about CDN
What is CDN?
A content delivery network is a geographically distributed network of servers that caches or delivers digital content from locations near requesting users.
Which Manning books explain CDN?
Building Web APIs with ASP.NET Core, Pro ASP.NET Core 7, Tenth Edition, Acing the Frontend Interview, Latency, Fundamentals of Cybersecurity and Server-Side WebAssembly.
What should I know before learning CDN?
Manning books that teach CDN usually introduce load balancing, web application, caching and CSS first.
What kinds of CDN are there?
Kinds of CDN include CDNJS.
What is CDN a kind of?
CDN is a kind of distributed file system. A distributed file system stores and manages files across multiple networked computers while presenting clients with a unified filesystem-like interface.
What is CDN also called?
CDN is also called content delivery network.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





