Loading...
Lets say we are a log collection platform for SaaS businesses.
Our system will log 1B events per day. Around 1B requests to the API.
Storage = 1B * 1KB ... = 1TB per day of storage.
Storage for a 2 year period = 1TB * 2 * 365 = 730TB --> 1PB adding an extra buffer for growth.
Define what APIs are expected from the system...
User: id, websiteUrl
LogEvent: id, type, timestamp, ownedBy
Quick Access Pattern -->
Given a User, read all log events
Given the heavy write workload that our system will have to bear, I think I will go with a NoSQL database.
For reading event log data, I will leverage the capabilities of a search engine, which will enable the scalability, high availability and fault tolerance requirements of the system.
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?