Live data from Hacker News

Netlify Edge Functions: A new serverless runtime powered by Deno

netlify.com

11–20 of 166 posts

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#12
post #2

Aaron from Deno here, happy to answer any questions you may have !

Is Netlify running Deno on their edge and not on Deno.com Deploy 's? Is this also what Slack, Vercel (?), and Supabase do?

Netlify and Supabase use Deno's infrastructure for code execution (https://deno.com/deploy/subhosting). Vercel hosts their edge functions on Cloudflare (nothing to do with Deno). Slack's Deno runtime is hosted on AWS.

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#13
post #6

This is a new concept for me, what is the use case for edge functions?

The first link in the article points to this: https://www.netlify.com/products/#netlify-edge-functions How to use them Drop JavaScript or TypeScript functions inside an edge-functions directory in your project. Use cases Custom authentication, personalize ads, localize content, intercept and transform requests, perform split tests, and more.

> Use cases

> A bunch of server functionality

Why is that the use case? I don't see how an edge function can be faster than a centralized server endpoint if it has to reach out to literally any other component of the system involved in auth / persistence

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#14
post #2

Aaron from Deno here, happy to answer any questions you may have !

Thanks! Any useful pros and cons vs Cloudflare Workers?

Workers can have persistent storage attached to them (as a KV store), I can't see whether this has anything similar.

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#15
post #2

Aaron from Deno here, happy to answer any questions you may have !

Thanks! Any useful pros and cons vs Cloudflare Workers?

One of the big reasons for going with Deno is that it's an open runtime closely based on web standards. You can download the open source Deno Cli and all code written for our edge layer will run exactly the same there.

As more and more front-end frameworks starts leaning in on running part of their code at the edge, we felt it was important to champion and open, portable runtime for this layer vs a proprietary runtime tied to a specific platform.

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#16
post #5

This is great news. I'm really rooting for a successful trend of Serverless runtimes, mainly as a weapon against rising cloud deployment costs. While the general trend today is to back the serverless environment with Javascript runtimes (Cloudflare runs its edge on top of V8, Netlify uses deno, most other serverless runtimes use nodejs), I'm optimistic that WebAssembly will take over this space eventually, for a bunc…

I agree about WASM. I am sort of worried that Deno may be too late tbh. Why would I bother with an interpreted language at all when I can code in any language I want and run it anywhere with WASM?

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#17
post #16
post #5

This is great news. I'm really rooting for a successful trend of Serverless runtimes, mainly as a weapon against rising cloud deployment costs. While the general trend today is to back the serverless environment with Javascript runtimes (Cloudflare runs its edge on top of V8, Netlify uses deno, most other serverless runtimes use nodejs), I'm optimistic that WebAssembly will take over this space eventually, for a bunc…

I agree about WASM. I am sort of worried that Deno may be too late tbh. Why would I bother with an interpreted language at all when I can code in any language I want and run it anywhere with WASM?

[deleted]

Re: Netlify Edge Functions: A new serverless runtime powered by Deno

#19
post #13
post #6

Earlier quoted context omitted.

The first link in the article points to this: https://www.netlify.com/products/#netlify-edge-functions How to use them Drop JavaScript or TypeScript functions inside an edge-functions directory in your project. Use cases Custom authentication, personalize ads, localize content, intercept and transform requests, perform split tests, and more.

> Use cases > A bunch of server functionality Why is that the use case? I don't see how an edge function can be faster than a centralized server endpoint if it has to reach out to literally any other component of the system involved in auth / persistence

It's just serverless architecture. It may not fit for every project.

We use the concept to add meta tags to our client-side-rendered webapp for search indexing. We can decouple our client app from our server and deploy each separately. We use "serverless functions" to add some meta tags that need to be added server-side.

Post reply on HN