Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Having spent the last few days trying to get Cloudfront with Lambda@Edge working, I'm excited to see this. Cloudfront is a mess and clearly Lambda@Edge is "cutting edge" at AWS (where cutting edge means "full of bugs")


You might want to try Cloudflare Workers instead. (disclaimer: I work at Cloudflare)


I assumed they were for service workers with SPAs. Not the case? The AWS landscape is so massive it's hard to understand what everything does. I'll check out CloudFlare workers, thank you.


Funny, I keep getting confused between CloudFront and CloudFlare and assumed this was another AWS product but it obviously isn't.

Do workers somehow operate inside your AWS stack via distributions of CloudFront? If not, that's probably not going to work, we have so much in S3, etc.

But, if that assumption is incorrect, can you point me to a document that suggests a transition path?


Cloudflare is actually a totally different company, yes! Here is more info about Workers: https://developers.cloudflare.com/workers/about/




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

Search: