In SQL, I have used nested sets to store hierarchical data. I am trying to do the same with Firebase. In theory, the hierarchy could be "n" levels deep, but in actuality will probably be only 5-7 levels deep.
I have done quite a bit of research. This Mongo DB documentation suggests only using nested sets on static trees. My data will change quite a bit over time. The same document leads to the conclusion that materialized path is the way to go.
Does anyone have experience with this?