Why should someone choose supabase over normal PostgreSQL?
Hey guys, I'm a big fan of Supabase and have used it for several side projects. Now, my team is building a B2C SaaS, inspired by Notion and GitBook, with a block-based editor, version-control, GitLab integration, and more.
Originally, we planned to use Supabase just for authentication, but now we're considering making it our primary database for multi-tenancy and concurrent users. Currently, our repository layer is built with Sequelize ORM and Postgres. We're contemplating swapping Sequelize with the supabase-js sdk, use supabase db keeping our business logic in the service layer.
However, we're a bit torn. Why should we switch from vanilla Postgres to Supabase, and is it a solid choice for long-term scalability?
Looking for insights from the community before we make a decision. Appreciate your thoughts! 😄
4 Replies
Not sure what you are considering vanilla Postgres but Supabase is a full Postgres install with only limit of no super user and extensions they provide unless you self host.
Thanks for the reply! Instead of just maintaining a db for auth we just thought why not use it for everything else we just do with postgres since its a full postgres but quite not sure if it has any potential cons do the same (nothing we could see as far now but still open for suggestions)
Also, one thing we could see is most companies/projects directly query the supabase db using PostgREST but we got a bit of business logic and couldn't find many projects that use supabase as db alone.
Sorry if it caused confusion, but when I mean vannila Postgres: https://www.postgresql.org/
Yes. That is what supabase is using. You have a direct database port to that.