InterviewBit Problems   Design Messenger


About the Design Messenger category (1)
Why do we need cache here (1)
Title of your commHave you tried out the newly launched patented EchoApp htt://echocommunicator.com for more ent (1)
How important is Availability for us? (7)
No explanation for Push from server (1)
Didn't get the clarity on Consistency; tight or eventual? (1)
So what's the DB schema for users, conversations and messages? (1)
Learning source for HBase (1)
How would the sendMessage API look like? (13)
Why is there no mention of a publish subscribe or a p2p messaging? (1)
How would a typical read query look like? (2)
Are joins required? (5)
Given the number of messages being sent, what is the amount of message sent data size we are generating everyday? (6)
What defines availability for a chat messenger? (1)
What are some other things we can do to increase efficiency of the system? (3)
What is the read-write pattern? (4)
How would the API for fetching most recent messages in a conversation look like? (4)
What would the API look like for the client? (4)
How important is Consistency for us? (2)
ClientMessageId not clear (2)
What is isdeltaupdate? (1)
Http protocol insufficient for real-time messenger apps (1)
What are the operations that we need to support? (3)
Persistent 2 way connections and more (1)
Do we need server side storage at all? (1)
What is the expected storage size? (3)
Question about how clients will receive the messages. For example, when two peopl (3)
Summary of building-mobile-first-infrastructure-for-messenger at FB (1)
What about security (1)
How would a typical write query look like? (7)