Loading...
Given long url will covert to short characters and will get saved to Database
when i visit the short url , my system will redirect me to the long original url.
List the key non-functional requirements (performance, scalability, reliability, etc.)...
short url creation should be very fast
Redirect should be fast within seconds
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
short url length= n
total characters = 62
daily total url that can be created = 62^n
total url creation < 62^n
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...
POST create(str(long URL)) => Short URL - 201 created
GET http://mysystem/{short url} - Redirected - 302
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...
Model - MySystem
Id - int
LongUrl - (Str)
ShortUrl - (Str)
CreatedAt - Datetime
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.