Hacker Newsnew | past | comments | ask | show | jobs | submit | KeychainPirate's commentslogin

It was a low-code "make your own website" platform. The sort of thing that was popular before myspace/facebook/medium style walled gardens took over.

Fastly bought it because they were/are desperate to pivot away from CDN, since CDN has negative margins.


OP works for Fastly, they're pushing a lot of "demos" like this in the hopes that one of them goes viral because nobody is using their serverless platform. Don't waste your time adding engagement to it, all they want is a few threads mentioning Fastly that don't mention the June 8th incident from 2021.


It's a proof-of-concept for a potential startup idea, not endorsed by my employer. I simply picked tech in arms reach.

Maybe in 2028 this could be a real thing, regardless of where it is running. An edge cloud does seem ideal for national live events though.


> An edge cloud does seem ideal for national live events though

OK, you almost had me believing you but "edge cloud" is 100% Fastly marketing speech. Any time I see somebody mention using Fastly, they turn out to be a Fastly employee. You've posted this demo three times already, give it a rest.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: