Testing the limits of Supabase and Postgres in a serverless environment
bibek-timsina.com.np
Testing the limits of Supabase and Postgres in a serverless environment
1–4 of 4 posts
Re: Testing the limits of Supabase and Postgres in a serverless environment
#2What I still wonder, what performance impact has it using Supabase e.g. from Hetzner or Digital Ocean - is this fast enough?
Re: Testing the limits of Supabase and Postgres in a serverless environment
#3What I still wonder, what performance impact has it using Supabase e.g. from Hetzner or Digital Ocean - is this fast enough?
I think it is generally fast enough just using Supabase js library, but if you want to manage your own pools and care about handling millions of concurrent requests, only then I think moving away from it might show some visible performance benefits.
Re: Testing the limits of Supabase and Postgres in a serverless environment
#4What I still wonder, what performance impact has it using Supabase e.g. from Hetzner or Digital Ocean - is this fast enough?
I think it is generally fast enough just using Supabase js library, but if you want to manage your own pools and care about handling millions of concurrent requests, only then I think moving away from it might show some visible performance benefits.
it's also worth noting here that a big benefit of supabase-js is that you can use it from the browser (assuming you have sufficient RLS policies). PostgREST is hosted on the same server as Postgres, so essentially you remove an entire network hop.