CDN
A content delivery network is a 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.
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.
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.
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.
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.