Database design

I would keep this as NoSQL DB because

a. we don't need strict consistency here i.e. ACID compliance does not seem a mandatory requirement here. I think it is fine if a redirect eventually say in 1 to 2 seconds redirects to the original url. Also, since the system is read heavy I believe the NoSQL DB will be more performative. referencing CAP theorem, which implies that we can only guarantee C (Consistency) or A (Availability) but not both. I am trading off C over A. We definitely need P (Partition Tolerance) for Fault tolerance and Scalability needs.

Schema: JSON

{

id: JSON<STRING>

short_url: JSON<STRING>

original_url: JSON<STRING>

last_accessed: JSON<TIME>

total_redirects: JSON<NUMBER>

country: JSON<STRING>

city: JSON<STRING>

is_active: JSON<BOOLEAN>

}

id: Unique Identifier

short_url: Shortened URL

original_url: Actual URL

last_accessed: When was it last used (this may be useful for caching)

total_redirects: How many times this has been used (this may be useful for rate limiting and saving against DDSO Attacks)

country: Location (this is useful for Load balancing, DNS etc.)

city: Location (this is useful for Load balancing, DNS etc.)

is_active: This is to decommission. this is useful for the cleanups

we should index on short_url for after redirects along with id which is used by all apis

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10