Thank you for your response. I am very new into system design area. I learnt a lot from your post. Are you using websocket in this design? Does it mean while user is viewing contents a hash table should store userID, serverID info?
I was thinking with NoSQL, we will have to keep two key value datastores.
1) userID(key) : a set data structure with postIDs -- O(1) insert and delete
1) postID(key) : a set data structure with userIDs -- O(1) insert and delete
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for your response. I am very new into system design area. I learnt a lot from your post. Are you using websocket in this design? Does it mean while user is viewing contents a hash table should store userID, serverID info?
I was thinking with NoSQL, we will have to keep two key value datastores.
1) userID(key) : a set data structure with postIDs -- O(1) insert and delete
1) postID(key) : a set data structure with userIDs -- O(1) insert and delete