Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Count the each view
List non-functional requirements for the system...
Fraud Prevention when counting
Highly available
High scalability
Real-Time updates
Data Integrity and Consistency
Eventual consistency
Estimate the scale of the system you are going to design...
Assuming we have 100 million DAU, each one views 5 videos on average, there will be 500 millions view per day.
Suppose the view record size is 100 bytes. The annual storage will be 500 million * 365 * 100 = 18.25 TB
Define what APIs are expected from the system...
GET /v1/view-count/{videoId}
Response view count for the videoId
PUT /v1/view-count/{videoId}
Add the view count for videoId by 1
Response code 200
Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...
Key-Value Database.
High throughput and low latancy
simplicity of data model
scalability
cache integration
real-time processing
Easy sharding and prtitioning
Key: VideoID
Value: Count
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?