3 ms·
It's convenient for content publisher and reduce infrastructure costs a lot. Just have the authenticated/editing part served directly and the published content
by LoSboccacc 10y ago
It's convenient for content publisher and reduce infrastructure costs a lot. Just have the authenticated/editing part served directly and the published content trough cdn.
- jacquesm 10y agoSo, retrospectively speaking: Was it worth it?
- LoSboccacc 10y agoto us, yes. a large customer signed up and we had a 300x traffic spike overnight, all eaten up by cdn. the first impression for a startup matters and them testing the service unannounced could have gone wrong in so much many ways.. cloudflare literally saved the day. the publishing part needs to be designed to leverage caching properly tho. however it's much easier to setup cloudflare+custom rules than a cdn push-on-change service