System requirements

Functional:

• user submit a long url , then create unique uri with 100 as max chars and mapping with original url
• other users request short url , the service will automatic redirect them to original url

Non-Functional:

• available with 99.9 % uptime
• Handling 10000 of requests concurrently
• Low latency to save or fetch proccess
• Avaliable over Consistance (AP)

Capacity estimation

• Daily Active User: 100,000 Users Per Day
• Peak Concurrent Users: 10,000 Concurrent Users
• Estimate Storage: 1,000,000 Records (URLs) * 800 b = 762 MB Per Day
• Redirects/sec : 10,000
• Cache Hit Rate : 95%
• Reads from DB : 10,000 * (1-0.95) = 500 reads/sec
• Outbound Bandwidth = (10000 * 700 / (1024 * 1024)) * 8 = 53.44 Mbps
• Inbound Bandwidth: ((1000 * 800) / (1024 * 1024)) * 8 = 6.1 Mbps

API design

The TinyURL service exposes a simple, secure REST API for creating and accessing shortened URLs. It uses JSON for communication, JWT for authentication, and rate limiting to ensure stability.

Endpoints

• Create Short URL
  • POST https://api.tinyurl.com/v1/shorten
  • Auth: Required
  • Rate Limit: 100 requests/min/user
  • Request:

{ "url": "https://example.com", "expiry": "2025-12-31T23:59:59Z" }

• • Success (200):

{ "short_url": "https://tiny.url/my-link", "expiry": "2025-12-31T23:59:59Z" }

• • Errors: 400 Bad Request, 401 Unauthorized
• Redirect to Original URL
  • GET https://tiny.url/{my-link}
  • Behavior:
    • 302 Found → Redirects to original URL
    • 404 Not Found → Short URL does not exist or expired

Security and Performance:

Security: JWT authentication, HTTPS enforced.

Rate Limiting: Protects against abuse and DDoS.

Database design

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...

High-level design

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...

Request flows

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...

Detailed component design

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...

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.

Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?