Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
okay so the following
List the key non-functional requirements (performance, scalability, reliability, etc.)...
performance
once the tweet is done it can be immediately seen by other people
the system should able to handle spiky load
what should be the max number of people you can follow
any capping on the number of twwets that you can do
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
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...
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.