Non-SQL database modeling

4

I'm developing a system that would use angular for the front-end part and the firebase for the database. Firebase uses a No-Sql database and I'm having a hard time understanding how I can model it. For example I have two nodes, "requests" and "requests-user", within requests I have a field that is called "type" will it be that I should create another node with "requests-type" to get faster and easier to filter , or will you have lots of information repeated?

I do not understand very well how to model a No-Sql database when I should create a node, if it is normal to repeat information to not go through an integer unnecessarily, if someone can explain me better

    
asked by anonymous 24.05.2017 / 16:04

1 answer

1

Non-SQL database work with a denormalization idea, roughly  is to repeat the same value for several nodes. Firebase itself has a YouTube channel that can help you. It helped me a lot to understand how to model my bank in Firebase.

Take a look at their playlist, it helped me a lot. PlayList Firebase

    
07.06.2017 / 17:08