InterviewBit Problems   Design Twitter


About the Design Twitter category (1)
I have been asked this question during an interview and I can say that the justif (5)
Design Twitter Are joins required? (3)
Design Twitter How important is Consistency for us? (4)
What is the number of users and traffic that we expect the system to handle? (3)
What would the API look like for the twitter client? (3)
Another resources which provides better details about how to solve interview question regarding designing Twitter (1)
I have been asked for Twitter LLD (1)
How important is technology maturity? (3)
How much data will we have to store? (5)
I still feel NoSql would have been a better choice over MySql here (2)
User-Follower relationship for celebrity (1)
Use 1 byte for user id? is it a joke? (2)
How would a typical write query (addTweet) look like? (2)
Design Twitter Is Latency a very important metric for us? (3)
Caching of User Feeds (1)
Which would fit better here, RDBMS or NoSQL? (4)
How many followers does every user have? (1)
How many times is a tweet favorited? (1)
Assuming the network of users, how many user to follower edge would exist? (1)
Design Twitter How important is Availability for us? (1)
What data would need with every Tweet we fetch? (1)
Would we need all the user profiles of users who have favorited a tweet? (1)
How would a typical read query (getUserFeed) look like? (1)
Design Twitter How do we handle the case where our application server dies? (1)
What data do we need to store? (1)
What would the database schema look like? (1)
Now the bigger question, How would we do sharding? (1)
Do we need special handling for spiky cases ( Users with unusual number of followers / Tweets with likelihood of getting unusually high number of favorites ) ? Think about the case when Katy Perry (with more than 70M followers) tweets (1)
Question: Approach2: Can we shard on recency(timestamp)? (1)