Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Supabase Edge Functions

supabase.com

Post reply on HN
Print view View original

11–20 of 68 posts

Re: Supabase Edge Functions

#11

Post by imilk »

jimmy2020 wrote: post #9
moralestapia wrote: post #7

Awesome! Congrats for shipping! 90% of the projects I work on are built on Firebase, our main worry with that is that we are locked-in, not only to "Firebase", but to Google as well which has a nasty history of just pulling the rug from under your feet without even telling you why. Having alternatives to try and implement is always a priority for us and Supabase now (w/ edge functions) seems to cover most of our use…

I am curious how the edge functions can replace Firebase?

Supabase offers a lot more than edge functions (db, auth, etc). Take a look at their website

Re: Supabase Edge Functions

#13

Post by inian »

jimmy2020 wrote: post #9
moralestapia wrote: post #7

Awesome! Congrats for shipping! 90% of the projects I work on are built on Firebase, our main worry with that is that we are locked-in, not only to "Firebase", but to Google as well which has a nasty history of just pulling the rug from under your feet without even telling you why. Having alternatives to try and implement is always a priority for us and Supabase now (w/ edge functions) seems to cover most of our use…

I am curious how the edge functions can replace Firebase?

If you are using Firebase Functions, it should be easy to port it over to Supabase Edge Functions. We also offer a Realtime database (Postgres), Auth and Storage as part of our stack.

Re: Supabase Edge Functions

#15

Post by jimmy2020 »

imilk wrote: post #11
jimmy2020 wrote: post #9

Earlier quoted context omitted.

I am curious how the edge functions can replace Firebase?

Supabase offers a lot more than edge functions (db, auth, etc). Take a look at their website

I know but the same goes for Firebase. As matter of fact, Supabase started as an open-source replacement for Firebase.

Re: Supabase Edge Functions

#16

Post by latchkey » 

  > 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 with easy control of DNS) as well as control the URLs (and even content) that ends up being sent to the GCF workers as well as caching of results in CF. It gives me a huge amount of flexibility and very little complexity.

Currently doing 1m hits/day through CF workers and it is ~$6/mo + ~$20 for GCP (including a Postgres db and heavy use of pub/sub).

All the other important things are done... CI/CD for the whole development flow with Github actions doing deployments on push to main, logging and graphs comes standard. The developer experience with both GCP and CF is top notch.

Supabase continues to be an interesting alternative, but I really don't see a reason why I'd go with them.

Re: Supabase Edge Functions

#17

Post by marcus_cemes »

Amazing work, kudos to the Supabase team!

> However, Supabase already offers a flexible solution for that - Database Functions! As such, for Supabase [Edge] Functions, we decided to deploy far-and-wide so that they are as close to your end-users as possible.

Does this mean that a choice has to be made between high latency (Edge Functions) and specialised SQL-only functions (Database Functions)? I see that cron-like triggers are still on the roadmap, is there a plan to have TypeScript functions that can run close to the database (or other resources)? Call me new school (as in not old school), but I prefer processing complex queries in a language that I feel comfortable working in, SQL is not that.

I know a lot of folks are huge fans of writing pure SQL, the lack of type safety and lack of good intergration with source control (I dream of a world where database schemas, functions, security access and the rest can be saved to source control for reproducibility) scare me.

Re: Supabase Edge Functions

#18

Post by [deleted] »

jimmy2020 wrote: post #9
moralestapia wrote: post #7

Awesome! Congrats for shipping! 90% of the projects I work on are built on Firebase, our main worry with that is that we are locked-in, not only to "Firebase", but to Google as well which has a nasty history of just pulling the rug from under your feet without even telling you why. Having alternatives to try and implement is always a priority for us and Supabase now (w/ edge functions) seems to cover most of our use…

I am curious how the edge functions can replace Firebase?

[deleted]

Re: Supabase Edge Functions

#19

Post by paxys »

getcrunk wrote: post #4

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

And Deno deploy itself likely uses AWS or the like under the hood. So you are paying base infrastructure costs plus the premium for every provider in the stack.

Re: Supabase Edge Functions

#20

Post by kiwicopple »

jimmy2020 wrote: post #12

It feels the CDN edge functions are the new Jamstack. It's fast but comes at a high cost and the excitement shifted from static pages to literally data distributed near the user.

edge functions was an obvious complement for us. we already have database functions [0] which can be executed through a REST api (database co-location is great for data-intensive operations).

Edge Functions are deployed to 29 regions globally, which means that you can use them for low-cost, low-latency operations.

[0] Postgres Functions: https://supabase.com/docs/guides/database/functions

Post reply on HN