Loading...
List non-functional requirements for the system...
Estimate the scale of the system you are going to design...
erDiagram
USER {
string id "Primary Key"
string username
string email
string bio
string profile_picture
}
TWEET {
string id "Primary Key"
string content
datetime timestamp
int likes
int retweets
string user_id "Foreign Key referencing USER"
}
RELATIONSHIP {
string follower_id "Primary Key"
string following_id "Primary Key"
}
ACTION {
string id "Primary Key"
string type
string user_id "Foreign Key referencing USER"
string tweet_id "Foreign Key referencing TWEET"
}
HASHTAG {
string id "Primary Key"
string tag
}
MENTION {
string id "Primary Key"
string user_id "Foreign Key referencing USER"
string tweet_id "Foreign Key referencing TWEET"
}
MEDIA {
string id "Primary Key"
string url
string tweet_id "Foreign Key referencing TWEET"
}
You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...
Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...
Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?