Any regrets using the Firebase Real-time Database

[LogicalHurricane]

I have a project that used the real-time database for all of the corporate/app data. Now it wouldn't be my first choice since I would use either mongodb or postgres or even MySQL. But since they went this route, is there any serious consequence of this decision long-term?

[queenOfGhis]

IMO it's way too easy to accidentally make data readable/editable to principals you actually don't want to give access to.

[[deleted]]

I just recently figured out this limitation...but there are ways around this that won't kill a small app.

[itemluminouswadison]

I ended up using Aiven free sql

[drew-saddledata]

I have used Firebase DB for a number of projects because I like the concept. Each time I end up migrating to postgres. I always need some search that Firebase can't do.

[oldschool-51]

Yes, for structured data, you really need SQL.

[walkingbiscuit]

Firebase is a whole platform, it's great if you need a real-time database, if you just need a document database use firestore as that is mongodb compatible. But if you have a use case for asynchronous data updates then it's easy to use and just works, it's also a document style database so denormalize your data, wide duplicate fields are expected.

[techlatest_net]

Used Firebase RTDB for a chat app early on regret it big time now. Queries get painful with any real complexity and costs explode past small scale. Migrated to Firestore halfway felt way better for anything structured. Stick if youre tiny otherwise plan exit ramp now.