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

# Static Content Delivery

**Static Content Delivery** enables organizations to deliver cacheable content efficiently through Medianova’s globally distributed CDN network. By caching static assets at edge locations, content is served from the nearest available Point of Presence (PoP), reducing latency, minimizing origin traffic, and improving application performance.

This category includes multiple CDN resource types designed for different content delivery requirements, including **Small CDN**, **Large CDN**, and **Video on Demand (VOD)**.

{% hint style="info" %}
Choose the resource type that best matches your content. Small CDN is optimized for static web assets, Large CDN for large file delivery and live streaming, and VOD for on-demand video streaming.
{% endhint %}

## Why Use Static Content Delivery?

Medianova's Static Content Delivery services provide a scalable and secure platform for delivering cacheable content.

* **Lower Latency** – Serve content from the nearest edge location.
* **Reduced Origin Load** – Cache frequently requested content at the edge.
* **Global Availability** – Deliver content consistently across geographically distributed PoPs.
* **High Scalability** – Handle traffic spikes without additional origin capacity.
* **Secure Delivery** – Protect content using HTTPS and SSL/TLS.
* **Performance Optimization** – Support compression, caching, and intelligent content delivery.

<figure><img src="/files/7nG1npW7e14gjzURLV4G" alt=""><figcaption><p>Medianova Static Content Delivery Architecture</p></figcaption></figure>

## Available Resource Types

### Small CDN

Optimized for websites and web applications that primarily deliver static assets such as images, CSS, JavaScript, and fonts.

Typical use cases include:

* Websites
* Corporate portals
* E-commerce storefronts
* Static web applications

### Large CDN

Designed for distributing large downloadable files and supporting live streaming workflows.

Typical use cases include:

* Software downloads
* Game patches
* Archives
* Large media files
* Live streaming (RTMP Push)

### Video on Demand (VOD)

Designed for delivering pre-recorded video using adaptive streaming technologies.

Typical use cases include:

* Video libraries
* Online education
* OTT platforms
* Media portals

Supports adaptive streaming formats including **HLS** and **MPEG-DASH**.

## Common Features

All Static Content Delivery resource types provide:

* Edge caching
* Custom domains (CNAME)
* HTTPS and SSL/TLS support
* Compression
* Global Anycast delivery
* Analytics and monitoring
* High availability

### Related Resources

* [Small CDN](/products/performance-cdn/static-content-delivery/create-small-cdn-resource.md)
* [Large CDN](/products/performance-cdn/static-content-delivery/create-large-cdn-resource.md)
* [Video on Demand](/products/performance-cdn/static-content-delivery/create-vod-resource.md)
* [Dynamic CDN](/products/performance-cdn/dynamic-content-acceleration.md)
* [Image Optimization](/products/performance-cdn/image-optimization-and-webp.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.