News for hackers. Stuff that matters.

A comment on S3 was down. Parent comment

Re:S3 was down by jsjohnst on Thursday September 14, 2017 @06:17PM (#15252948)
Look, I know what I'm talking about. Just because you can purge faster because of a different deployment doesn't mean that's the case for everyone. "Fast Purge" is not available for every type of deployment.
[ Parent | on HN ]
Re:S3 was down by nothrabannosir on Thursday September 14, 2017 @08:02PM (#15253501)
> Look, I know what I'm talking about.

Thanks for replying, but unless you're willing to explain to the rest of us why so, why bother? I can't make heads or tails of this pissing contest thread.

[ Parent | on HN ]
Re:S3 was down by notyourday on Friday September 15, 2017 @08:29AM (#15256540)
You are confused.

"Site Delivery" is purged globally within 7 minutes.

"Fast purge" enabled products (site delivery) is purged globally in under 20 seconds.

All assets for websites are site delivery. Only media services family of products are not site delivery. Those purge within a couple of hours. If you are someone who uses media services products, you know how to force Akamai to go back to origin globally instantaneously and how to trigger invalidation. In media services you should never serve stale.

[ Parent | on HN ]
Re:S3 was down by jsjohnst on Friday September 15, 2017 @02:56PM (#15259733)
As I said, it depends on your deployment. Thanks for the reply and confirming what I said was correct, that under some deployments it can be a multi-hour purge.
[ Parent | on HN ]