# Dynamic Content Acceleration

**Dynamic Content Acceleration** delivers time-sensitive and user-specific content faster by intelligently caching dynamic responses at the **CDN edge**.\
Unlike static assets, dynamic content (such as personalized dashboards, API responses, or search results) is generated for each request, which can increase server load.\
Medianova’s **microcaching** technology allows these responses to be cached for very short durations — even a few seconds — dramatically improving responsiveness while keeping data up to date.

This feature is available for **Dynamic CDN Resources** and can be managed through the [Medianova Control Panel](https://cloud.medianova.com).

#### Why Use Dynamic CDN?

Dynamic content caching enhances both **speed** and **efficiency** for high-traffic applications. It helps you:

* **Reduce origin load** – Serve frequent requests directly from CDN edge nodes.
* **Improve page responsiveness** – Cache HTML and API responses for short durations.
* **Lower bandwidth costs** – Decrease redundant origin requests.
* **Scale efficiently** – Handle large traffic spikes with consistent response times.
* **Balance freshness and performance** – Configure cache rules to keep data relevant without overloading the origin.

{% hint style="warning" %}
Use Dynamic CDN for applications where content changes often but not on every request — such as product listings, search results, or pricing data.
{% endhint %}

#### Key Features

* **Microcaching** – Cache dynamic responses for seconds or minutes to optimize performance.
* **Full Page Caching (FPC)** – Cache entire HTML pages to reduce origin queries.
* **API Caching** – Store API responses for repetitive or frequent calls.
* **Edge-based Caching** – Execute caching at CDN edge locations to minimize latency.
* **Custom Page Rules** – Exclude sensitive or real-time pages such as checkout or admin panels.
* **Granular Cache Control** – Configure individual TTLs (cache durations) for different endpoints.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FROfF1wi7S9Iit9m0sinH%2Fdyn.png?alt=media&#x26;token=2fe5354f-cb7c-4125-b8db-03ed2c378ad9" alt="" width="563"><figcaption><p>Medianova Dynamic CDN</p></figcaption></figure>

#### How It Works

1. The origin server generates dynamic content in response to user requests.
2. The **Dynamic CDN edge** caches the response for a short, configurable duration (e.g., 5 seconds).
3. Repeated requests within that duration are served instantly from the edge cache.
4. Once the TTL expires, the CDN refreshes the data from the origin to ensure freshness.

{% hint style="success" %}
A product API returning inventory counts can be cached for 10 seconds — enough to handle hundreds of identical requests without stressing your database.
{% endhint %}

#### Important Configurations

<table><thead><tr><th width="174">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Cache Time (TTL)</strong></td><td>Determines how long dynamic responses are cached before being refreshed. Shorter TTLs maintain freshness; longer TTLs improve performance.</td></tr><tr><td><strong>Page Rules</strong></td><td>Define which paths should or should not be cached (e.g., exclude <code>/checkout</code>, <code>/admin</code>, or highly dynamic pages).</td></tr><tr><td><strong>API Endpoints</strong></td><td>Apply caching selectively to repetitive API calls (e.g., product listings, autocomplete, or pricing).</td></tr></tbody></table>

{% hint style="warning" %}
Setting cache time too low may reduce cache efficiency, while setting it too high can risk serving outdated data. Start small and adjust gradually based on analytics.
{% endhint %}

#### Best Practices

* Exclude **personalized** or **transactional** pages (like `/checkout` or `/profile`) from caching.
* Cache short-lived API responses to improve responsiveness.
* Regularly monitor cache hit ratios to fine-tune TTLs and rules.
* Combine Dynamic CDN with **Rate Limiting** and **WAF** for performance and protection.
* Use **Compression** and **WebP Optimization** to further reduce load times.


---

# Agent Instructions: 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:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.