Menu

Stop Using Firebase for Everything: Why I Switched to PostgreSQL (Supabase)
🖼️

Stop Using Firebase for Everything: Why I Switched to PostgreSQL (Supabase)

DEV Community·Ujjwal Sharma·6 months ago
#bQ2KngSm
Reading 0:00
15s threshold

1. The Hook

We’ve all been there. You start a new project, you want to move fast, so you plug in Firebase. It feels like magic at first. But what happens 6 months down the line when your app scales, your data becomes relational, and suddenly you are paying a premium just to run complex queries? You hit the NoSQL wall.

2. The Problem

The biggest trap modern developers fall into is treating a NoSQL document store (like Firebase/Firestore) as the ultimate solution for every single app.

Here is where the pain starts:

Vendor Lock-in: Moving away from Firebase once your app is live is a nightmare.

Complex Queries: Need to filter data based on multiple nested conditions? Good luck writing that without fetching half your database.

Pricing Surprises: It's free until you accidentally run a bad query in an infinite loop and wake up to a massive bill.

3. The 'StackByUjjwal' Solution

It's time to respect Relational Databases again.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.