You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 9, 2025. It is now read-only.
I would be really interested in learning more about your data structure architecture decisions. Such as:
Why not combine room-messages and room-metadata?
What is room-users? Is it list of userIDs for each room-id? If so, then see why not combine with the above two nodes as well for a general room node
Is user-names-online a list of userIDs: boolean?
With regards to storing the name with each message - what if a user edited his/her name? Is that possible inconsistency something you are willing to allow for faster access (versus having to access '/users/user-id/name'?
In any case, some discussion on the architecture decisions would be great for those of us who are new and trying to learn how to architect an app with firebase!
I would be really interested in learning more about your data structure architecture decisions. Such as:
room-messagesandroom-metadata?room-users? Is it list of userIDs for each room-id? If so, then see why not combine with the above two nodes as well for a generalroomnodeuser-names-onlinea list of userIDs: boolean?namewith each message - what if a user edited his/her name? Is that possible inconsistency something you are willing to allow for faster access (versus having to access '/users/user-id/name'?In any case, some discussion on the architecture decisions would be great for those of us who are new and trying to learn how to architect an app with firebase!