Why I'm using Firebase and not Supabase for my next project
By any chance, if you read my blogs, guess you know I'm launching 6 startups in 6 semesters. On my last product, I used Supabase as my primary backend.
Though I really enjoyed the developer experience of Supabase, but for my next product, I decided to get back to Firebase and here's why 👇
💸 The biggest issue I had with Firebase is their pricing model!! But for NotionCommerce almost all my queries will be done by Notion APIs. So I'm quite certain I won't exceed their free plan even if I reach thousand active users.
🤝 Firebase made it so simple to integrate with other Google services like oAuth, and analytics. They recently also added the Extensions feature to easily integrate with third-party services as well. Which I'm really looking forward to trying out.
😴 Supabase pauses the application after 7 days of inactivity.
🏠 Working with Supabase locally wasn't a very pleasant experience for me! especially when syncing with the live server. But I suppose that's more of a SQL issue than Supabase, which brings me to my next point 👇
🛠️ After going back and forth, I have come to the conclusion that NoSQL is far superior for prototyping an Idea.
Hey Arif, Supabase cofounder here - I'm sorry to see we didn't live up to your expectations, but I've shared this feedback with the team and we'll make sure we improve for the next developer. Thanks for trying us out, and thanks for all the useful feedback!
I really like Firebase. I like NoSQL but you do need to think about data retrieval upfront. With relational you model the data more logically and let the query engine figure out data access.
Yes but I feel at a very early stage when you are just trying to figure things out, You need to do changes to my DB from time to time. Which feels very hard to do with SQL.