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.

1) API Layer: 2 APIs; post (to get short url), & get (to get longer url)

2) URL Service:

a) checks if the url is valid, is it already present in cache/db?

b) generates unique short url & stores in db (mapping of short-> long url, created_at, expiration, click_count=0)

3) unique id generation:

a) create base 32 encoding of auto-increment id

b) create base 32 encoding of randomly generated 6-8 character string

c) use consistant hashing to avoid duplications

4) DB: url mapping, created_at, expiration, click_count

nosql cassandra DB as we need to store large amount of data

5) Cache: redis. HOT urls based on click_count to be stored here. whenever the expiration is met for a given url, that url is replaced with the next most_clicked url

Submissions

Displaying Solutions with Scores Ranging from 1 to 10