Hacker News new | past | comments | ask | show | jobs | submit login

Not necessarily - I think the target audience is different.

If you are administering an internal datacenter in a company, then you can utilize this to offer a serverless env. to application developers in your company, and then those developers would benefits similar to that of AWS lambda/CF workers etc.

Someone will obviously have to manage servers, but in addition to it, it is also quite a bit of work to support orchestration of ephemeral functions, and a nice open source framework is definitely a huge help there.




That's a good point... you mean like enterprises with big IT teams who want to in-house Cloudflare Workers and run it on their own infrastructure?

That makes sense if they already have the network but not necessarily the easy to use APIs for serverless. Kinda a way to overlay new dev modalities onto old infrastructure, I suppose.


Not just old infrastructure, there are plenty of good reasons to run your own infrastructure beyond "that's what we've always done".

Edit: Good reasons not in the sense of "everyone should do it" but in the sense of "for some situations it's the right choice"




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: