Streaming Video Encoding & Packaging Pipeline  ·  View 19 of 22  ·  Operations

Rendition Lifecycle

Seven states, and the reason the ring actually closes.

Editable source SVG draw.io All views
Planned a rung in a recipe Generated batch or on demand Gate-passed scored, structural, decoder Published in a manifest revision Hot top demand tier Demoted nearline / coldline Evicted regeneration beats retention Rendition as cache digest scores swap demand decay horizon demand returns Rendition Lifecycle — The Loop That Closes Application we own Decision point Interface / broker Data store Risk / gap The ring closes because eviction is not an end state: a request for an evicted digest re-enters at Generated. v 1.0 · owner Media Platform Architecture

Eviction is not an end state

  • A request for an evicted digest re-enters at Generated. That is what makes this a lifecycle rather than a retention schedule.
  • The eviction rule is economic, not temporal: evict when regeneration cost falls below retention cost over the policy horizon.

The centre is the design decision

  • "Rendition as cache" is in the middle because every transition on the ring is only legal under that reading. If renditions were publications, Demoted and Evicted would be data-loss events.

Assumption

  • Assumed ≥ 70% of catalogue hours held at the cheapest tier or not held at all, and rendition storage ≤ 18% of total storage spend. Both are targets the tiering policy is tuned against.