3 ms·
[Supabase cofounder] Firebase is really only bad if/when you decide to move - usually because of scaling/performance issues. For example, you can only query on
by kiwicopple 6y ago
[Supabase cofounder]
Firebase is really only bad if/when you decide to move - usually because of scaling/performance issues. For example, you can only query one document per-second. Once you decide to migrate away, it's very painful - but the truth is all migrations are painful.
This is one of the reasons we chose postgres. If you want to migrate away, you can just "take your database" with you. PG can scale with the best of them.
Edit: I said "you can only query one document per-second" but this is supposed to be "you can only query each document once per-second". Sorry!
- londons_explore 6y agoSo are you saying there is no way to get a database dump of firebase, so you have to query both your old and new databases (and deal with all the resulting consistency issues) for a transition period unless your service wants downtime?
- tlarkworthy 6y agoFirebase has backups to cloud storage, there is no problem obtaining a dump of your data, but that's only one part of a migration
- almostarockstar 6y ago>you can only query one document per-second That's not true. You can't query any single document more than once per second, which is very different. You can certainly query many separate documents per second.
- kiwicopple 6y agoSorry - I intended to write that but I guess I had a freudian slip. You're 100% correct - each document only. Let me put a note
- galactus 6y ago"you can only query one document per-second".. uhm, that doesnt sound right, it would make firestore useless for all intents and purposes. The only limitation I know that sounds close to that is 1 _write_ per second for the _same_ document.