title: Firebase DB structure for scale
body: <p>I understand that this question could be open-ended, but I would like the answer. I have a firebase db and a model called widgets. Each user can obtain many widgets, and each company can create multiple widgets. Right now I save widgets to a "widget" child - key and again to the specific company, under the company key and "widget" child - key. Once the user accepts the widget, I save it there also. </p>
  
  <p>Is this a normal process? I have another model that I save in 6 different locations. Ahhhhh.... I dont know if I should keep going if my whole db structure is not correct. I want to know this answer based on a large scale of users. Or should I just be saving the unique key under the userID and then "get" the keys, then the info? That just sounds like more work and I would rather have the speed on the user side and let the db take time. I guess I also just dont know if the db can handle that much updating. 3 updates per widget * 100,000 users... Will this cause issues?</p>