Live data from Hacker News

Supabase Edge Functions

supabase.com

31–40 of 68 posts

Re: Supabase Edge Functions

#31
post #23

> Serverless compute options can be broken down into two broad categories: > Containers as a Service (e.g. Google Cloud Run, Fly.io) > Functions as a Service (e.g. Cloudflare Workers, Fastly Compute @ Edge, Suborbital) There are also Google Cloud Functions, which is odd to not mention here. For what I'm working on, I've put CF Workers in front of my GCF's. This allows me to terminate the SSL at the CF Worker (along w…

The Google Cloud Functions are not really good compared to CloudFlare Workers :/ The GCF are regioned, slow to start and behaving like an on-demand temporary cloud instance, than an actual FaaS offering.

Using golang cloud functions. I have a constant stream of hits, so there are always available functions.

Connecting to cloud sql postgres and serving a request that hits the database takes under 1s. Hot request/responses are ~20ms.

My hits are all US based, so I plopped myself into Central. No issues there either.

Re: Supabase Edge Functions

#32
post #30

Earlier quoted context omitted.

> Do the functions "freeze" once the response body has been sent back? Just checked with the Deno team. These functions should not be used as "background workers" - perhaps that is something we explore in the future. It will work for a short time in theory, but it's not guaranteed. > How does keeping a connection pool work between function invocations Supabase offers several options here. You can either use the API (…

> These functions should not be used as "background workers" Thanks for checking on it. We actually had to create a Cloudflare worker based "fire-and-forget" system to allow our Vercel functions to shoot off background tasks. Was hoping to replace that. > Supabase is a popular database hosting service for Prisma Agreed! We actually use Supabase as our backend for Willow[1] and use Prisma when writing backend function…

> The dream would be to have a great DX experience around using insert/update triggers to call Supabase functions to run background tasks

We have something for this: Function Hooks (soon to be renamed "Async Triggers")[0]. They are still in alpha, but the extension [1] is getting close. It was important to build something which works with PG background workers so that it's non-blocking. We'll make quick progress on this now that we've released Edge Functions.

> sending notifications or updating related rows

Tune in for tomorrow's announcement - it's related.

[0] Function Hooks / Async Triggers: https://supabase.com/blog/2021/07/30/supabase-functions-upda...

[1] https://github.com/supabase/pg_net

Re: Supabase Edge Functions

#33
post #8

I'd love to learn more about how its making use of Deno. I have been loving Supabase lately, both for hacking away at side projects. I have been thinking about moving some of my own backends over to Supabase.

Feel free to ask any specific questions about our Deno usage which isn't covered in the blog post. Inian is in the comments and will be able to cover anything technical

Re: Supabase Edge Functions

#34
post #4

This uses deno deploy under the hood, which interestingly enough still doesn't list pricing because it is pre-release.

The latest preview screenshot I've seen from the Deno discord had the following. I believe official pricing will be out in a few weeks.

Free plan: 100k requests per day with up to 10ms CPU time per request.

Pro plan: $5/mo + $0.50/million requests per month with up to 50ms CPU time per request.

Re: Supabase Edge Functions

#35
I'm excited about the new functionality and find the cause of not defaulting to Cloudflare Workers commendable, I worry a little about the long term viability of Deno Deploy - is there a backup platform that Supabase edge could deploy to in the event of a Deno Deploy acquisition, or even better, is Supabase going to acquire Deno Deploy?

Re: Supabase Edge Functions

#37

I'm excited about the new functionality and find the cause of not defaulting to Cloudflare Workers commendable, I worry a little about the long term viability of Deno Deploy - is there a backup platform that Supabase edge could deploy to in the event of a Deno Deploy acquisition, or even better, is Supabase going to acquire Deno Deploy?

> is there a backup platform that Supabase edge could deploy to in the event of a Deno Deploy acquisition

Yes, we could host this all ourselves (since the Deno runtime is open source) on AWS, or more likely we'd work with someone like Fly who have a globally-distributed platform like Deno Deploy.

> is Supabase going to acquire Deno Deploy

There's no chance of that happening. We couldn't afford them. Deno will be a huge company - and rightfully so, their product is best-in-class

Re: Supabase Edge Functions

#40

I'm excited about the new functionality and find the cause of not defaulting to Cloudflare Workers commendable, I worry a little about the long term viability of Deno Deploy - is there a backup platform that Supabase edge could deploy to in the event of a Deno Deploy acquisition, or even better, is Supabase going to acquire Deno Deploy?

> is there a backup platform that Supabase edge could deploy to in the event of a Deno Deploy acquisition Yes, we could host this all ourselves (since the Deno runtime is open source) on AWS, or more likely we'd work with someone like Fly who have a globally-distributed platform like Deno Deploy. > is Supabase going to acquire Deno Deploy There's no chance of that happening. We couldn't afford them. Deno will be a hu…

Thanks for taking the time to respond to my concerns kiwicopple - I'm looking forward to giving your edge functions a spin then!
Post reply on HN