Detailed component design

• Hash-based ID algorithm such as base62 or random generation

• Collision detection

handling collisions :

• Distributed vs central generator

• Edge CDN rationale

• Data-center cache (Redis)

Cache the short url as key and long url as value

helps for faster look ups with defined ttl

• Eviction/TTL policy

• Per-IP or per-token policy

• Burst handling/back-off strategy

Database design

generate short url from uuid from long url string
To scale the database need to higher capacity
As the data is create only , we cna use nosql databases like cassandra
Database design like : long url, short url ,created time stamp , expiry time stamp , user id
User details : User id, user name , create time stamp, update time stamp
Use normalization to refer to data about meta data like user , domain
Partitioning Key as hash of short url , as hash of url are based on UUID , short url will be evenly distributed across shards, looks up also distribute across the shards
Partitioning based on hash using crc 32
Index on Short URL column help for faster look ups
Eventual consistency is ok for this use case
Data Normalization - use Normalization Users and URL