6 ms·
I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the
by chrisweekly 6y ago
I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.
- ksec 6y agoThe problem with Runtime at Edge is that they are extremely engineering intensive, given it isn't just hosting but the whole software stack involved. ( See CloudFlare Workers for Example ) Which is sort of outside the sweet spot that DO is currently enjoying or operating in. I am not sure if it is a sound strategic decision to persuade. Although I would certainly love to see competition in that area.
- chrisweekly 6y agoWell yeah, if you care enough about performance that it matters whether the "server" runtime is at the data center or the edge, it's kind of a given it won't all be completely automagic. But it is, thankfully, becoming an increasingly straightforward path to tread.
- chrisweekly 6y ago^ beyond annoyed w myself for writing "Cloudfront EdgeWorkers" (not even a thing) when I meant CloudFlare Workers.
- kentonv 6y agoWe were going to call it that, bought the domain names and everything, but a competitor registered a trademark on the name the week before we launched. Oops. Remember kids, always register your trademarks.
- HappyDreamer 6y agoWhat were you going to call it? The competitor, was it DigitalOcean? (Or am I misunderstanding :-) )
- kentonv 6y agoEdgeWorkers (I work on Cloudflare Workers.) (But in my previous comment I totally missed that chrisweekly said "Cloudfront" and not "Cloudflare", lol.)
- HappyDreamer 6y agoOk thanks for explaining :-)