| I love Firebase for what it provides "in the box". Auth, noSQL database, cloud functions a ton of added features like real time updates an a lot more. My use case is mostly for quickly developing personal, and "side apps" for work that complement our primary applications. It excels at that. There's a lot of comparisons in here about querying in here those are fair-ish / true-ish, I do think that's also missing what Firebase is "about", at least that's not what I've found it useful for. If you're thinking about weighty sever side business logic and SQL queries ... yeah Firebase isn't built around SQL, it's not built to optimize big business logic and SQL like queries (granted, there are still ways to do these things). Firebase isn't likely replacement for your enterprise CRUD app that carries with it a ton of logic for each and every possible CRUD action. And you do have to stop and think about how you are going to structure your collections, docs and so on. Having said that I think NOT being the solution for complex CRUD apps is what makes Firebase pretty great. I think the idea that business logic on the server being kinda wonky on Firebase is true generally. At the same time: "Once again, with Cloud Firestore you could put this code into Cloud Functions and use them as a business logic layer, but it's messy and requires giving up some of the platform's other features like reactivity and optimistic updates." I think that statement is deceptively broad. Just using cloud functions doesn't eliminate optimistic updates and so on, the effect is limited to when or how you use them... |