Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
Given a short Url redirect to original long url
Given a long url generate short url n redirect
Generating alias
List the key non-functional requirements (performance, scalability, reliability, etc.)...
Scale: how many URLs created/day, how many redirects/day
redirect should be fast
reads more less writes sort of 100:1 ratio
should redirects basically never go down
a stored short URL should never get lost
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...
/urlshortener/read will direct to reads which will hit hte cache and check if reads r present n access theshort url n redirects
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...
Dynamo DB for all reads/writes I will use elastic cache redis for hot links read which will improve the reads
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.