System requirements

Functional:

• generating a short url from a URL
• list my URL URLs
• get full URL from short URL

Non-Functional:

• app should be highly available
• high performance

Capacity estimation

• estimation for generating the short URL
  • 200 requests per second
• estimation for redirecting to the Full URL from a short URL
  • 2000 requests per second

• Average data size estimation
  • size of id, size of URL
    • 16 byte for Id
    • average 100 byte for every URL
  • maxim URL is 1000 byte for every URL

API design

• post /url
  • full url
• get /url/:short-url

• users

Database design

table name: urls

field: id: uuid

field: fullUrl: string

High-level design

load-balancer for service

service shorting-URL

cache: =>

database: NoSql

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

• load balancing should happen DNS for global coverage
• No SQL is used here because
  • data schema doesn't have relations
  • fast retrieval of data
  • replication is easy for global coverage
• cache should be used to retrieve the top hit short URLs

Trade offs/Tech choices

• sql vs nosql
  • data schema doesn't have relations
  • fast retrieval of data
  • replication is easy for global coverage
• uuid vs sequins
  • uuid should be used because its faster to generated
  • easy to scale
  • supported by nosql

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?