DEV Community

loading...

Discussion on: Supabase: ten months of building.

Collapse
supabase_io profile image
Supabase Author

Hey John, thanks for the feedback. We're implementing the features of FIrebase, but we're not creating a 1:1 mapping. For example, we use Postgres instead of a NoSQL store. This is on purpose - we want to make the platform scalable, and Postgres is proven to scale.

Why would I choose this instead of Hasura?

Probably a matter of preference! There are quite a few similarities. Joe highlighted some of the differences in his response.

Ultimately we're both open source and contributing to other open source tools like Postgres, so it's great for you and the community :)

Collapse
johncarroll profile image
John Carroll

We're implementing the features of FIrebase, but we're not creating a 1:1 mapping.

Fair enough. I guess the point I was trying to make is that, for me (a Firebase user for about 2 years who is aware of, but has never used, Hasura), I don't find the current Supabase marketing materials that compelling. But it's important for me to acknowledge that, in general, I'd rather use a GraphQL API than another proprietary javascript one. While I like the Firestore API, it's definitely a negative that it's proprietary.

Ultimately we're both open source and contributing to other open source tools like Postgres, so it's great for you and the community :)

You are correct! Best of luck.

Thread Thread
techronin profile image
Collin Thompson • Edited

Yeah it’s a bit “YCombinator” the a,b,c for x,y,z. I’ve used all three and while there are similarities, what makes Supabase stand out for me is the authentication, Postgres and that it’s open source. I do wish it had some of the “functions” of firebase and the GraphQL capabilities of Hasura—I’m really liking the security features as well as how easy it is to manage, query, and edit the database. It’s hella fast too.