Overview
When content production and viewers are far apart, the first request and newly published files deserve particular attention. Evaluate publishing and reading separately before choosing cache and copy policies.
This is regional planning guidance, not a claim of particular nodes or storage in Australia, New Zealand or other markets. Confirm the actual available scope separately.
Observe distance on the cold-request path
Repeated visits may be handled well by caches, while first requests, invalidations and infrequent objects still need the source. Test these cases instead of considering only warm-cache results.
- Measure first reads of new content in target markets.
- Check errors, retries and recovery when a source is unavailable.
- Compare sustained large transfers with concurrent small resources.
Keep cross-region publishing consistent
With multiple content copies, release order should not expose missing files or old manifests. Prepare assets before changing the public entry point.
Before publication
Verify integrity, captions and manifest references so the complete public version can be read.
During updates
Keep an appropriate transition window for old versions, including long-open pages and active playback.
On withdrawal
Define which addresses and caches must be invalidated, and verify the state at each source.
Choose around audiences rather than a map's center
Test according to actual traffic shares in Australia, New Zealand and other served markets. Preserve differences and compare them alongside cost and maintenance effort.
| Subject | Decision evidence |
|---|---|
| Source placement | Publishing practicality and audience cold reads |
| Need for copies | Update frequency, origin load and storage cost |
| Delivery experience | Loading, playback and downloads on real devices |