> 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/dynamic-content-acceleration.md). # Dynamic Content Acceleration Accelerate personalized, database-driven, or API-based content with Medianova’s Dynamic CDN. Cache dynamic responses at the edge to reduce origin load and deliver faster user experiences. Dynamic Content Acceleration improves the delivery of content that is generated by an application rather than served as static files. Unlike images, JavaScript, or CSS, dynamic responses are created in real time and often depend on user sessions, request parameters, application logic, or backend data. Medianova's Dynamic CDN reduces response times by combining intelligent request routing, edge caching, optimized origin communication, and configurable cache policies. These capabilities improve application performance while maintaining content freshness.

Dynamic Content Acceleration using a Dynamic CDN Resource

## How dynamic content differs from static content Static content can typically be cached for long periods because it rarely changes. Examples include: * Images * CSS * JavaScript * Fonts * Downloadable files Dynamic content is generated by the origin application when a request is received. Responses may vary depending on: * User authentication * Session data * Cookies * Query parameters * API requests * Database queries * Geographic location Because responses can change frequently, Dynamic CDN applies configurable caching policies instead of long-term edge caching. {% hint style="info" %} Dynamic Content Acceleration is intended for content that changes frequently but does not necessarily require regeneration for every request. {% endhint %} ## How Dynamic Content Acceleration works When a request reaches the CDN, the edge server evaluates the configured cache policy before contacting the origin. 1. A client sends a request to the nearest Medianova edge server. 2. The CDN evaluates the request and checks whether a valid cached response is available. 3. If a cached response exists, the edge server returns it immediately. 4. If no valid cache entry exists, the request is forwarded to the origin. 5. The origin generates the response. 6. The CDN caches the response according to the configured policy. 7. Subsequent requests can be served directly from the edge until the cache expires. This approach reduces origin traffic while maintaining up-to-date application content. ## Acceleration techniques Dynamic Content Acceleration combines multiple optimization techniques to improve response times and reduce backend load. #### Microcaching Caches dynamic responses for very short durations, typically a few seconds. This significantly reduces repeated requests during traffic spikes while preserving data freshness. #### Full Page Caching Caches complete HTML pages for applications where pages do not change for every user or request. #### API Response Caching Caches API responses based on configurable cache policies, reducing repeated backend processing for frequently requested endpoints. #### Edge-based delivery Serves cached responses directly from the nearest CDN edge location, reducing latency for end users. #### Optimized origin communication Reuses and optimizes connections between edge servers and origins to reduce connection overhead and improve cache-miss performance. #### Configurable cache policies Allows different cache durations and behaviors for specific URLs, API endpoints, or application paths. ## Typical use cases Dynamic Content Acceleration is commonly used for applications that generate content on demand, including: * E-commerce platforms * Product catalogs * CMS-driven websites * Customer dashboards * Search results * Pricing services * REST APIs * GraphQL APIs * News portals * SaaS applications ## Best practices To achieve the best balance between performance and content freshness: * Cache only responses that can be safely reused. * Exclude personalized and transactional pages from caching. * Use short TTL values for frequently updated content. * Configure Page Rules for endpoint-specific cache behavior. * Monitor cache hit ratios and adjust cache policies as application behavior changes. * Combine Dynamic CDN with WAF and Rate Limiting to improve both performance and security. ## Related features Dynamic Content Acceleration works together with several Dynamic CDN capabilities.
FeaturePurpose
Page RulesApply different cache behaviors to specific URLs or application paths.
Browser Cache RulesControl how browsers cache dynamic responses.
Edge Cache ExpirationConfigure how long responses remain cached at CDN edge locations.
Query String CachingDefine whether query parameters create separate cache entries.
CompressionReduce response sizes before delivery.
WAFProtect applications from common web attacks.
Rate LimitingControl excessive or abusive traffic.
## Configure a Dynamic CDN Resource To use Dynamic Content Acceleration, create a [**Dynamic CDN Resource**](/products/performance-cdn/dynamic-content-acceleration/create-dynamic-resource.md) in the [**Medianova Control Panel**](https://cloud.medianova.com). The configuration process includes: * Defining the origin server * Configuring SSL/TLS * Setting cache behavior * Applying Page Rules * Configuring security features Continue with [**Create Dynamic Resource**](/products/performance-cdn/dynamic-content-acceleration/create-dynamic-resource.md) to configure a new Dynamic CDN Resource. --- # 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/dynamic-content-acceleration.md?ask=&goal= ``` `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.