Is Firebase Too Restrictive for Certain Projects?

0
14
Asked By CuriousDolphin32 On

Hey everyone! I've been diving into Firebase for almost a year now thanks to my new job. Coming from a Rails and Postgres background, I appreciate features like background jobs and flexible relationships in traditional databases. I enjoy using Firebase for my work; its tools and client SDK make it easy to get feedback quickly. The authentication system and deployments are straightforward too. However, while trying to use Firebase for my personal projects, I often feel like I'm struggling with it rather than benefiting from its features. I've run into issues like not being able to fetch certain keys from documents, facing challenges with complex relationships, and limited querying options. Even though I know I can work around these hurdles, it seems like I'm always battling the system. Is it possible that I'm just not structuring my data correctly, or is Firebase not suitable for the types of projects I want to pursue? I'd love to hear your thoughts on Firebase and experiences with NoSQL databases!

4 Answers

Answered By DevGuru2023 On

I share a similar background with Laravel and Postgres. Firebase is excellent for rapid development and real-time features, but it can be a hassle when you require complex queries and relational data. It's not about skill—it’s simply a different tool. I opted for Supabase for my personal projects since it uses Postgres underneath, allowing for easier querying while offering good auth and real-time features. If you haven't tried Supabase yet, it might be worth checking out.

Answered By NewCoder123 On

I’m in the same boat! I started using Firebase for my first project recently. Really curious to see other people's thoughts on it as well.

Answered By SQLFanatic4Life On

Firestore does have some benefits, but it also has its downfalls. From what you've described, you might be happier using a SQL database like Postgres.

Answered By TechSavvyNinja On

I’ve been using Firebase since before Google acquired it. My perspective is that it’s a tool with a specific purpose. I see people trying to fit it into scenarios it wasn’t designed for, and that creates issues. Some of the challenges you’re facing are common with document-oriented databases. They often require careful planning of your schema. When you start needing bidirectional relationships, things can indeed become messy. For real-time data syncing, Firebase shines—it's super reliable and requires minimal code, but you’ve got to manage your query subscriptions wisely.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.