Detailed component design

For the shortending service, we can use a-z, 0-9, 36 character in total, so, we use 32-based encoding.

For the Mongo DB database structure, we use key-value store form like, in this way, the shorten URL can find the corresponding long URL very quickly. And we will do sharding by the hash value of the short url, to minimizing the hot-spot problem. To solve the hash-collision, we can do a second-hashing. And we will use a Master-Slave mode to reduce the load and to avoid single point of failure.

For the Cache, we will use Redis, and use LFU as its eviction policy to try to reduce the load to database, besides that, we can add other fields like expiration time to better control its life cycle.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10