Functional Requirement :

1) User generate short url for big url

2) User is able to redirect to the orginal link from the short url

3) User can create profile and create url associated with its profile

1) Scalable -> add more url, and server more redirect

2) Latency -> 5ms ?

3) Available -> as much as possible

4) Read Heavy

API Design

Get /shortCode -> redirect to big url

Post { bigurl } -> return { shortUrl , expiry }

High-Level Design

client -> gateway -> user Service -> userDb

UserDb { id , userName , name , emailId , phoneNumber }

Postgresql vs ?

WHAT SHOULD BE THE OTHER DATABASE I SHOULD CONSIDER FOR TRADEOFF AND THEN MAKE A COMPARISON

client -> gateway -> url Service -> urlDb

urlDb{ id , shortUrl , longUrl , expiry }

Redis vs Postgresql

REDIS BECAUSE THERE IS EXPIRY FEATURE AS WELL AS SHORT URL KEY VS POSTGREQ SQL FOR QUERY , read is faster in redis, with faster query than index and also more concurrent reads and also ttl

Detailed Component Design

High available -> Url and User service should be horizontal scalable and managed by eks so they are not

Low Latency -> reduce the call using redis, instead of db

Horizontal Scalability -> make the services horizontal scalable

Concurrent request ? how is that a issue, like multiple read can be supported using redis, and even if multiple reads on same row is it supported

Cache miss ? do we have to persist it somewhere else ?

Avoid Collisions -> avoid collision of url generation so in this we can have 7 bit uuid generation which will be unique