For those using Supabase in production, I'd love t...
# off-topics
stibbs
08/09/2021, 3:33 AMFor those using Supabase in production, I'd love to hear what/where your backend is while we wait patiently for Supabase Functions? AWS Lambda? Cloudflare Workers? Google Cloud Run? A node/go/elixir server hosted wherever?
v
Volkan
08/09/2021, 3:34 AMim looking at nextjs api for simple stuff
Volkan
08/09/2021, 3:34 AMwill most likely have a node server (not serverless) as well
x
Xyo
08/09/2021, 3:48 AMAWS Lambdas (Vercel, but it’s technically lambdas). Serverless goes nicely with Supabase since you can use PostgREST on the backend and offload a lots of operations to the client directly.
Xyo
08/09/2021, 3:50 AMCloudflare Workers (bundled) is another good runner here since they use execution time rather than cpu time for execution (in terms of resource usage), so while the worker waits for PostgREST to respond, you’re not consuming resources.
s
stibbs
08/09/2021, 4:14 AMWhen you say Vercel, do you specifically mean APIs/endpoints in nextjs or svelte etc that are deployed to vercel?
That's definitely a big + for Cloudflare Workers that I hadn't thought of
x
Xyo
08/09/2021, 4:21 AMI use SvelteKit with vercel so that covers the page rendering too
Xyo
08/09/2021, 4:21 AMBut yeah, could just leave the frontend part aside, serverless endpoints do work very nice with Supabase
Xyo
08/09/2021, 4:22 AMIf you use next I’d say Vercel is the obvious choice, otherwise I’d recommend Workers
Xyo
08/09/2021, 4:22 AMOnly reason I don’t use workers myself is because I do some JS processing that can go over the 50ms limit
s
stibbs
08/09/2021, 4:58 AMWhat are we talking in terms of complexity in your sveltekit endpoints on vercel?
Is it mostly kept to my view needs this data, my view needs to update that type functions?
x
Xyo
08/09/2021, 4:59 AMThey are pretty basic but they can also be pretty complex 🤷♂️
s
stibbs
08/09/2021, 4:59 AMI'll give it a go, just hoping to prevent a footgun lol
x
Xyo
08/09/2021, 5:00 AMthere's realistically nothing you would do in nodejs that you wouldn't do on lambdas
Xyo
08/09/2021, 5:00 AMthe only difference is state management
Xyo
08/09/2021, 5:00 AMActual AWS lambdas are still nodejs (Workers are a v8 derivate), you can run the same code, you just don't have continuity
Xyo
08/09/2021, 5:00 AMThe lambda can die if no traffic, or new ones can spawn if too much traffic
Xyo
08/09/2021, 5:01 AMSo you wouldn't do stuff like
const onlineUsers = []Xyo
08/09/2021, 5:01 AMbut there comes the beauty of Supabase Auth, since it's external, it solves the most common serverless problem - auth state
j
JW
08/09/2021, 9:52 AMWe use Cloud Run & Kotlin for our backend. We have a flutter app for Android and iOS.