5
I’m developing a system that will use angular for the front-end part and 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 called "type" will I create another node with "requests-type" to get faster and easier to filter, or will have a lot of repeated information ?
I did not understand very well how should be made the modeling of a No-Sql database when I should create a node, if it is normal to repeat information not to go through an integer unnecessarily, if someone can explain me better
Does your doubt have anything to do with it? https://firebase.google.com/docs/database/web/structure-data or is specific to the business model you are creating?
– Pagotti
yes, it is related to the structure of the bank, I had already taken a look at this link you posted, but had not understood very well, for example, according to this example has no problem to create equal nodes in difirent places, thus facilitating the search, however I think it becomes more difficult to create, edit and delete because it has to change in several places
– Juliano Sirtori
I think I got it. Your question is more general in the sense of which best practices to take an ER model to an object tree structure like JSON instead of leading to an SQL structure, considering how Firebase makes access to this data.
– Pagotti
that’s right, I work with relational model, using databases like mysql, Postgresql, Oracle. When using a Nosql bank I am a little lost since the structure is another.
– Juliano Sirtori