Customers usually start with ShieldCache alone and add packaging once the first codec migration makes doing it in-house unattractive.
Masters in, adaptive renditions out, with a per-title audit trail.
Sits between a public CDN and your storage. The CDN sees an origin that never stampedes; your storage sees a client that reads each segment once.
Concurrent misses for one segment become a single upstream read. This is the whole point of the service during live windows and premiere nights.
Manifests, init segments and media segments get separate freshness rules. Dynamic paths can be marked no-store so a body is never replayed into the wrong session.
Read timeouts are set per resource. Low-latency live holds connections open far longer than a VOD segment does, and one global number cannot serve both.
Byte-range requests are forwarded unmodified so seeking and progressive download behave the same as they would against the origin.
A resource is defined by five fields: upstream URL, the segment path, connect timeout, read timeout, and the cache rule. Everything else has a default that we will argue about only if it becomes a problem.