News for hackers. Stuff that matters.

A comment on Fastly S-1. Parent comment

Re:Fastly S-1 by siwyd on Sunday April 21, 2019 @07:45AM (#19711644)
> Not anywhere close. Your cache invalidation takes forever. Ability to assign tag objects does not exist. Engaging "professional services" to make a config change like it is 2002?

Akamai also has a fast purge these days, sub 5 seconds as well I believe. Works nicely.

[ Parent | on HN ]
Re:Fastly S-1 by notyourday on Sunday April 21, 2019 @09:44AM (#19712042)
Fast purge only works on certain kind of objects in certain kind of configurations, not to mention the idea of "I would like tom make 20k purge requests in a second via an API" is met with stares.

Fastpurge is a hack.

[ Parent | on HN ]
Re:Fastly S-1 by siwyd on Sunday April 21, 2019 @10:37AM (#19712235)
Interesting. I only have experience with the occasional simple (manual) purge and I could verify the object was invalidated quickly. Can you elaborate on an example config where this goes awry?
[ Parent | on HN ]
Re:Fastly S-1 by notyourday on Sunday April 21, 2019 @12:43PM (#19712974)
Fast purge works with all kinds of site delivery ( and site delivery based ) products. Unlike modern CDNs Akamai other products ( such as for example VOD and media services ) do not live in the same object space and hence are not fast purge compatible.

You would think purging a video stream would be the same as purging a standard site delivery object, after all it the stream is http(s) accessible .m3u8 and a pile of .ts chunks but that's not the case -- in some cases it can take up to one hundred and twenty minutes.

[ Parent | on HN ]
Re:Fastly S-1 by siwyd on Monday April 22, 2019 @05:16AM (#19717528)
I see, thanks for the info.
[ Parent | on HN ]