3 ms·

I am excited about this. Two questions: 1) Does scaling a Supabase app basically just boil down to scaling a Postgres database? Firebase (Firestore) claims the

I am excited about this. Two questions: 1) Does scaling a Supabase app basically just boil down to scaling a Postgres database? Firebase (Firestore) claims they can do like a million concurrent connections & 10 megs per second of writes. Any idea of the scaling limits of Supabase? Totally understand if this isn't on the radar yet, it is not really a concern for most applications. 2) Do you have a built in authentication solution? One of the pleasures of Firebase is the built in authentication that mostly just works by enabling it. Happy that you are building an alternative to Firebase.

kiwicopple 6y ago
> Does scaling a Supabase app basically just boil down to scaling a Postgres database? Correct. We will soon add vertical/horizontal scaling (early next year). For concurrent connections, we use PostgREST[1] for RESTful calls, and an Elixir/Phoenix server [2] for realtime data. This reduces the number of connections to your DB, handling concurrency in the middleware. We are building the benchmarks now, but "enterprise scale" is top of mind with everything we are doing. > Do you have a built in authentication solution? Yes, we use GoTrue [3] for authentication, and we use Postgres Row Level Security for authorization. You can read more about it here: https://supabase.io/blog/2020/08/05/supabase-auth https://supabase.io/blog/2020/08/05/supabase-auth [1] http://postgrest.org/en/v7.0.0/ http://postgrest.org/en/v7.0.0/ [2] https://github.com/supabase/realtime https://github.com/supabase/realtime [3] https://github.com/netlify/gotrue https://github.com/netlify/gotrue