Use Cases and Best Practices [EN]
Typical use cases
HLS/MPEG-DASH functionality is especially useful for:
Video-on-demand (VOD) services
✓ Stable segments with high cacheability
Over-the-Top (OTT) and media delivery services
✓ Need for efficient global distribution
Live streaming platforms
✓ Frequent playlist updates
✓ High segment request volume
Workflows with mixed caching requirements
✓ Dynamic manifests + static media assets
Best practices
1. Use Short TTLs for Playlists
Playlists should be refreshed frequently to ensure players receive up-to-date segment lists.
Recommended: keep low TTL (e.g., around default 10s)
Avoid long caching for playlists unless your content is static
HLS feature User Guide [EN] | MPEG-DASH feature User Guide [EN]
2. Use Longer TTLs for Segments
Media segments are typically unchanged once generated.
Use longer TTLs to reduce origin load and improve cache hit ratio
HLS feature User Guide [EN] | MPEG-DASH feature User Guide [EN]
Especially important for high-traffic streams
3. Enable Specific Mode for Fine Control
If your streaming workflow requires optimization:
Use Specific mode to:
Adjust TTLs per HTTP status code
Handle edge cases (e.g., errors vs successful responses)
HLS feature User Guide [EN] | MPEG-DASH feature User Guide [EN]
4. Honor Origin Headers When Needed
If your origin already defines cache behavior:
Keep “Honor response TTL headers” enabled
Ensures consistency between origin and CDN
HLS feature User Guide [EN] | MPEG-DASH feature User Guide [EN]