Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...

Use a NoSQL database to store short URL to long URL mappings. NoSQL database like Cassandra or MongoDB could be used for high throughput reads and eventual consistent writes. Since the Short URL service is a read-heavy system we would need to redirect with low latency. Redis could be used given the amount of in memory storage available. It would reduce database load by retrieving the most frequently used short URLs from the memory before reading from disk storage.

To support low latency we could use CDNs to host the frequently used short URLs distributed regionally low response times during reads.

Additionally, to support fault tolerance, since the Short URL service can tolerate eventual consistency, to ensure high availability, we can have partitioned database based on the base62 keyed URLs, and have two replicas in a leader follower schema. Writes would go to the leader and the follower databases the updated short URLs would be propagated to the followers while the most frequently used URLS would be stored in the CDN and also in memory in the Redis Cache.

An API Gateway could be used to direct requests to the services. We should separate write servers from read servers.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10