Edge Cache and CDN Platform · View 05 of 29 · 2 · People and journeys
The trough, and the answer
- One PoP, GRU, has not acknowledged. The status page names it rather than reporting 94% done. GRU was on a transit incident and withdrawn, so it is serving nobody; when it returns it replays the log before announcing again (view 17).
- A tag addressing two million objects costs the same as a purge of one URL. The PoP stores one row with a timestamp and compares against it on lookup (ADR-13).
Decisions it forces
- Assets are versioned URLs and never purged. Only the HTML and the price API are invalidated, and each path records which strategy governs it.
- Prices use expire, not purge. If the origin struggles under the refetch, standard paths can still serve the old price for a declared 60 seconds, and that trade was approved by the property owner beforehand.
- The purge API returns 202 with a sequence number. Acknowledgement is a separate, observable outcome, never assumed from a successful call.
Numbers
- 99% of PoPs acknowledge within 5 s p95 and 30 s p99. A typical run takes under 2 s.
- Per-property purge budget of 50 records per second sustained with a burst of 5,000, so one team's bulk publish cannot delay another team's purge.
