What are the current scaling limitations of Supabase? Do you have a sense of how many req/s etc it can handle? Firebase has the nice property that it's really easy to get started but it will scale to millions of users (ignoring the dev cost of restricted querying), I'm curious how that will work with managed Postgres.
Are there any plans for a typed/generated client down the line?
I see I replied to that tweet - it's a great list of criteria.
> What are the current scaling limitations of Supabase?
We haven't benchmarked it yet, but we have one of our power users doing ~1M API calls per week. That's on a t3a micro server. Soon, we will give you the ability to scale up and out. We don't plan to abstract away the database layer too heavily because it break the "no lockin" promise. We will more likely make it very easy to run a High Availability cluster (Ant has a background in HA).
> Are there any plans for a typed/generated client down the line?
100%. We're planning a Supabase CLI which will do this (+ give you the ability to spin up new projects etc).
What are the current scaling limitations of Supabase? Do you have a sense of how many req/s etc it can handle? Firebase has the nice property that it's really easy to get started but it will scale to millions of users (ignoring the dev cost of restricted querying), I'm curious how that will work with managed Postgres.
Are there any plans for a typed/generated client down the line?