Cloudflare Developers•3y ago

supabase does look interesting, seems like it can be selfhosted as well

AAA supabase does look interesting, seems like it can be selfhosted as well

sathoro•5/14/23, 7:51 PM

yeah it can be, is almost entirely open source

AAOP•5/14/23, 7:52 PM

i wish it'd been more mature when i started this project ;P

sathoro•5/14/23, 7:52 PM

we use it for auth and CRUD stuff

sathoro•5/14/23, 7:52 PM

ha yeah stuff is moving fast the last couple years

AAOP•5/14/23, 7:52 PM

this projects from 2018.. still chugging.

AAOP•5/14/23, 7:53 PM

predates workers i believe

sathoro•5/14/23, 7:56 PM

it is a good time to start a project now

sathoro•5/14/23, 7:56 PM

DOs and workers have been a literal game changer

AAOP•5/14/23, 7:56 PM

'soon' is always a good time to start a project

TTom Sherman How? Don't think you'd be able to run that on a worker

sathoro•5/14/23, 8:22 PM

I meant once the TCP comes out. In meantime use Supabase or PostgREST

sathoro•5/14/23, 8:22 PM

why

sathoro•5/14/23, 8:23 PM

pgbouncer will queue the connections

sathoro•5/14/23, 8:23 PM

that is half the point of using it

sathoro•5/14/23, 8:23 PM

also workers stick around for a while you could cache the requests locally I think. but establishing a connection to pgbouncer doesn't take that long

sathoro•5/14/23, 8:24 PM

I'm not saying you would run it in a worker

sathoro•5/14/23, 8:24 PM

you run it on a server close to the database

sathoro•5/14/23, 8:24 PM

and connect to it from the worker

sathoro•5/14/23, 8:24 PM

running it in a worker would make no sense lol

sathoro•5/14/23, 8:24 PM

now we are just going in a circle lol

sathoro•5/14/23, 8:25 PM

already have this exact convo above: workers-and-pages-discussions

sathoro•5/14/23, 8:25 PM

well, people who have ever run postgres in production would think that

sathoro•5/14/23, 8:26 PM

and people who haven't would quickly learn

sathoro•5/14/23, 8:26 PM

but again, if you want to keep it easy then you can get the benefits of Postgres by using a service like Supabase (this is what we do)

TTom Sherman The thing you're missing above is that a DO-based pool would unlock more feature...

sathoro•5/14/23, 8:27 PM

yeah... I get that. but it doesn't exist yet lol. so I am talking about real world practical things here and you are talking about theoretical things that might exist in the future and won't be production ready for several months

sathoro•5/14/23, 8:28 PM

I would rather use a battle tested connection pooler that handles edge cases than a DO library used by 5 people

sathoro•5/14/23, 8:28 PM

even popular DO libraries like itty-durableitty-durable have their issues in production

sathoro•5/14/23, 8:28 PM

so I am little cynical after running into these issues

sathoro•5/14/23, 8:29 PM

lets just say I wouldn't eagerly use a brand new DO Postgres connection pooler in prod when there are many other options

TTom Sherman The other option is to just pay a serverless pg SaaS to do it for you I guess

sathoro•5/14/23, 8:30 PM

yeah that is what I suggested:

but again, if you want to keep it easy then you can get the benefits of Postgres by using a service like Supabase (this is what we do)

sathoro•5/14/23, 8:31 PM

you get other nice things with it like webhooks and a whole auth system

sathoro•5/14/23, 8:31 PM

not just postgres

TTom Sherman That's still using http right? Assume there's some perf impact there or nah?

sathoro•5/14/23, 8:35 PM

yeah it is over HTTP. we barely call Supabase from our Workers, we try to keep them separate as much as possible (most requests made from the client/browser). so haven't tested it. but Supabase keeps a connection pool on their end so you would just be getting hit with creating the HTTP connection but I'm sure we could cache that between requests pretty easily in Workers

sathoro•5/14/23, 8:35 PM

Supabase uses PostgREST which has its own connection pooler from my understanding

sathoro•5/14/23, 8:36 PM

it would be the same performance I think as calling something like pgbouncer directly

sathoro•5/14/23, 8:37 PM

I don't think that in practice the difference between TCP and HTTP would really be measurable for this sort of use case. the bottleneck is always going to be Postgres by far

supabase does look interesting, seems like it can be selfhosted as well

Similar Threads

Similar Threads

Similar Threads