This blogpost is bitter and weird. Cloudflare is announcing an improvement in their platform, and Fastly is responding with a weird flex about losing their competitive advantage?
As a customer, I don't really care which vendor had the edge 10 years ago, I just want to compare features today. Does Fastly support WebSockets yet? This just highlights how little Fastly is doing recently.
I'm not sure there'd be much benefit to using shielding with WebSockets, since the traffic wouldn't be cached/collapsed. You can still shield HTTP traffic on the same domain being used for WebSockets.
This blogpost is bitter and weird. Cloudflare is announcing an improvement in their platform, and Fastly is responding with a weird flex about losing their competitive advantage?
As a customer, I don't really care which vendor had the edge 10 years ago, I just want to compare features today. Does Fastly support WebSockets yet? This just highlights how little Fastly is doing recently.
> Does Fastly support WebSockets yet?
It does! Can be served at the edge or passed through to origin.
According to the docs WebSockets are still incompatible with WAF and Origin Shield...
https://docs.fastly.com/products/websockets
If I'm not using Origin Shield, and I can't use WAF, why would I bother with Fastly when AWS Cloudfront is a fraction of the cost (And has WebSockets): https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...
I just don't understand what Fastly has been doing for the past few years, it seems like they're just selling bandwidth these days.
I'm not sure there'd be much benefit to using shielding with WebSockets, since the traffic wouldn't be cached/collapsed. You can still shield HTTP traffic on the same domain being used for WebSockets.
WAF could be nice though.