4 ms·

A different runtime from nodejs is more a feature than an issue. The worker runtime is much closer to deno than to nodejs from a philosophy standpoint and i exp

A different runtime from nodejs is more a feature than an issue. The worker runtime is much closer to deno than to nodejs from a philosophy standpoint and i expect a lot of synergies between cf workers and deno in the future. the cf workers being as much compatible with the service worker api as possible makes them the only faas solution close to a web standard, so vendor lockin will only be an issue until compatible offerings appear. A killer argument for this approach is also that you can be sure you can run the cf worker code also in a browsers service worker (with minimal modification). This allows more flexible architectures and also more unified development between backend and frontend.

jFriedensreich 6y ago
Also regarding the domains: cloudflare routes the requests to the edge centers based on dns anycast, so cloudflare workers cannot really be seperated from the dns functionality of cloudflare, see it as a faas offering inside your worldwide distributed dns. If that is not what you want, it is still possible to use cf workers with worker domains and use your own domain and dns setup
- pier25 6y ago
  My point is not so much about the tech but actually that SSL for SaaS is out of reach for most startups or small tech companies.
  - jFriedensreich 6y ago
    ahhh, sorry i did not know "SSL for SaaS" was a product name for a specific feature. I totally agree, this would have been really nice to be able to offer my clients, but is currently not really accessible. There are a few things like this such as custom error page etc. Lets hope more enterprise offerings will be more accessible for smaller projects in the future...
pier25 6y ago
I totally get that, but it's just a limitation that is not obvious at first.
- jFriedensreich 6y ago
  true, cloudflare communicates that extremly well in talks they give about it and online presentations, but the documentation is often not as easy to read

jFriedensreich 6y ago

Also regarding the domains: cloudflare routes the requests to the edge centers based on dns anycast, so cloudflare workers cannot really be seperated from the dns functionality of cloudflare, see it as a faas offering inside your worldwide distributed dns. If that is not what you want, it is still possible to use cf workers with worker domains and use your own domain and dns setup

pier25 6y ago
My point is not so much about the tech but actually that SSL for SaaS is out of reach for most startups or small tech companies.
- jFriedensreich 6y ago
  ahhh, sorry i did not know "SSL for SaaS" was a product name for a specific feature. I totally agree, this would have been really nice to be able to offer my clients, but is currently not really accessible. There are a few things like this such as custom error page etc. Lets hope more enterprise offerings will be more accessible for smaller projects in the future...

pier25 6y ago

I totally get that, but it's just a limitation that is not obvious at first.

jFriedensreich 6y ago
true, cloudflare communicates that extremly well in talks they give about it and online presentations, but the documentation is often not as easy to read