Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
List the key non-functional requirements (performance, scalability, reliability, etc.)...
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
100m daily active users
10m users simultaneously
avg 10mb/tweet - 100m tweets per day - 1tb new per day
should have 1000tb storage
Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...
//post a tweet
POST /tweets/
auth token for user
request:
{
tweetId: 123,
content: "abc",
contentURL: "xyz.com",
date: 1000,
}
response 201 created - successfully posted tweet
//follow other users
POST /users/follow/
auth token for user
request:
{
userId: 123,
date: 1000
}
response 202 accepted - followed user
//like save or repost tweets
POST /tweets?action="like"
auth token for user
request:
{
tweetId: 123,
date:1000
}
response 202 accepted - liked tweet
//get personalized feed
GET /tweets/feed/[userId]
Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.
Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.