5 ms·
> I'm maybe less bullish on the prospect of coding to a particular CDN's Javascript API (which is not a problem Deno has). Workers, Sites, Workers KV, and now
by ignoramous 5y ago
> I'm maybe less bullish on the prospect of coding to a particular CDN's Javascript API (which is not a problem Deno has).
Workers, Sites, Workers KV, and now Durable Objects... it is much more than a JS API. I recently experimented with Durable Objects and they do make developing against a kv-database much simpler, even if it is limited while in beta. Our development is all-in Cloudflare atm, but we also look fondly at fly.io to move other workloads (over from AWS) that Cloudflare won't / can't support.
- tptacek 5y agoSorry, I didn't mean to sound dismissive! The thing I'm not bullish about is people programming directly to a set of CDN APIs. What I like about Deno is that it runs anywhere. There's clearly an upside to programming directly to your CDN! It lets you integrate more ambitiously!
- babelfish 5y agoWhat kind of workloads have you moved over to CF that you have found were a good fit for the Workers model?
- ignoramous 5y agoWeb server, rate limiter, fronting actual servers (api gateway / reverse proxy), user auth / user data (db), and file hosting (downloads).