> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/c/cdn-content-delivery-network.md).

# CDN (Content Delivery Network)

A system of distributed servers that deliver pages and other web content to a user based on the geographic locations of the user, the origin of the webpage, and a content delivery server.

A Content Delivery Network (CDN) is a geographically distributed group of servers that caches content close to end users. The primary purpose of a CDN is to reduce latency by serving content from a location physically closer to the user rather than from a single origin server.

CDNs handle a significant portion of internet traffic, caching static assets like images, stylesheets, and scripts. Modern CDNs have expanded beyond static content to include dynamic content optimization, web application firewalls, bot management, and serverless compute at the edge.

For API management, CDNs provide a natural infrastructure layer for deploying API gateways at the edge. By placing gateway logic on CDN nodes, API requests are processed closer to the end user. This reduces latency, enables geographic routing decisions, and provides built-in protection against DDoS attacks. Cloudflare Workers, for example, allows running API gateway logic directly on CDN edge nodes worldwide.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.serverlessapigateway.com/glossary/c/cdn-content-delivery-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.