Yep data modelling and querying capabilities is a real deal breaker in Firebase.

Something as simple as filtering by 2 or more values becomes ridiculously tedious.

http://stackoverflow.com/questions/26700924/query-based-on-m...

I completely agree that on its own, the querying functionality can be quite tedious for anything complex. I linked to this solution on the comment above as well: https://github.com/davideast/Querybase

> Querybase is in an experiment and not for production

Also since Firebase doesn't allow more than one filtering field with orderByChild(...) I'm guessing Querybase will do all the work on the client. This is less than ideal since the data has to be downloaded first.

Querybase is also making permutations of all the data you may wish to query. Needlessly taking up space on your server that will have to be retrieved. Wasted bandwidth etc.

I wouldn't call this an "issue" as much as a "limitation". Just as you can develop a data denormalization process for any use case, you can develop one for Firebase.

Here's a practical example of doing joins with Firebase (written by David East who is also the star of that video you linked): https://github.com/davideast/Querybase

They must be using something akin to Cassandra to require something like that