Hacker News Reader

Comment by nicoburns | Hacker News Reader

Supabase is pretty exciting. Our product at work was initially hosted on Firebase, and while there were some really nice aspects to it (auth, realtime querying) we had a whole host of problems with the limited querying power of Firebase's non-relational model. So we've gradually been porting everything over to Postgres (with Hasura for realtime queries).

I have a question about the new auth functionality:

In the blog post it shows configuring auth rules via a GUI. Is there also support for a code-first approach where these rules are stored in a (sanely human editable) text format, which is then synced up to the server via a CLI or similar. I've found that this is absolutely crucial in order to ensure consistency between dev and prod environments, and to be able to spin up testing environments.

For that matter, is there an easy way to run the superbase stack locally as a local dev environment?

View on HN

> Is there also support for a code-first approach

We plan to build git integrations which will handle migrations (including Policies) and two-way syncing between git and postgres.

For now, you'd have to handle this yourself (we give you root access to your Postgres database)

> is there an easy way to run the superbase stack locally

We had(have) a docker image but it's outdated. We're in the process of updating for local development. It handles the middleware, but not the UI (for now)

I'm very excited about Supabase for the same reasons (https://twitter.com/vimota/status/1201622087888068608)! Having Auth is a huge step toward making it an easy replacement for Firebase.

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).

Amazing thank you!

> Is there also support for a code-first approach where these rules are stored in a (sanely human editable) text format.

We follow this approach. ACL is generated as JSON which then pass through REST & GraphQL middlewares. Completely extensible. Do watch us out [1]

[1]:https://github.com/xgenecloud/xgenecloud

Reply on news.ycombinator.com