Loading...
The user can see twittes
The user can send twitte
The user can like/dislike one twitte
The user can comment twitte
Speed Performance, Low-latency, Scalabilty, A/B Testing,
1 twitte 140 characters 10kb , DAU: 1Billions,
get call user first load feeds:
get :
url: /feeds/v1/
header: {
user_id, token, bucket_id, experiment_id, location_info, device_info,
}
params: {
query, tags[etc, news, sports], sorted_by:[relevent/timeline], cursor_id, limit
}
response: {
user_info.
twitee_lists:[{
twitee_id,
title,
context,
short_description,
image/video,
commentList :['good', 'nice', 'lookgood']
}],
bucket_version,
next_cursor
}
post call, user create twitte: /new_twitte/v1
post call, user like/dislike one twitte
post call, user make some comment to the twittee
Timeline DB
TwitteEventDB
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?