Design Twitter for millions of users

👷‍♂️ In progress: We are writing our own solutions
We find that solutions online don't do justice to real FAANG interviews. So, we're writing our own.
to get these early versions. Unsubscribe anytime.

🙋 Here are some details you should know about this question:

What data will you store for each tweet? (tweet ID, user ID, timestamp, text, media link, etc.)

How will you design for billions of tweets, millions of users, and high fan-out (e.g., celebrities with millions of followers)?

How will you index tweets and store user timelines? (e.g., in separate timeline storage or as pointers to tweet objects?)

What will you cache (timelines? tweet metadata?) and where (e.g., Redis)?


← Back to Main Table