3 ms·

Doesn't this sort of... miss the entire point of serverless? It's an API framework, with syntax like serverless, but without the whole advantage of serverless:

Doesn't this sort of... miss the entire point of serverless? It's an API framework, with syntax like serverless, but without the whole advantage of serverless: not having to manage individual servers, CDNs, networking, mirroring, etc. So you end up with something like Flight PHP or Next.js's API routes, but still needs to be deployed and then manually managed and scaled. Cloudflare Workers is innovative not because it's isolated or follows a particular syntax, but because they allow very fast and cheap functions to be run, globally, with zero maintenance on the customers' parts. Just write code and click save and it's available at data centers all around the world, instantly, for not even pennies. Blueboat would be incredibly difficult to scale up and maintain across clusters. Correct me if I'm wrong, but there is no way to deploy this at a cost even remotely similar to what Cloudflare offers, since individual customers don't have their economies of scale (and peering agreements).

lf-non 5y ago
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.
- technobabbler 5y ago
  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.
  - wongarsu 5y ago
    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"

lf-non 5y ago

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.

technobabbler 5y ago
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.
- wongarsu 5y ago
  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"