Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...

The URL creation service itself can function in a variety of ways so long as a unique hash can be created based on some parameter provided. Typically in other systems that do the same thing, the system will avoid using characters that can be confused for one another such as lowercase L and 1, or capital o and zero in some font formats.

This however, should be able to be overridden by the passage of custom tinyURL hashes if and only if they adhere to a specific set of constraints by defined by us which can be decided at a future point. However the maximum number of characters should probably be in roughly the 8 to 10 character range as that give us enough lee way to have up to 1 billion tiny URLs even with custom instances that are used.

Maybe it would also be good to have a list of the most recent URLs that have been generated in order to remove duplicate signals that have recently been registered

The user registration service is called only when in particular scenarios allowing for creation, updating and delete functionalities to be built from within. There may be some threading options when it comes to the creation/updating of accounts based on traffic timings or perhaps these transactions against the mySQL db can be splattered across multiple pods.

A smaller service should perhaps be considered for scanning the database and cache for tinyURLs that have outlived their welcome based on the TTL values used in either. In the case of the LRU cache it would likely be phased out on its own, but the scan from the database should still indicate instances that are no longer valid and those ones should be filtered out. This TTL value can be argued to be 1 year, 2 years or perhaps a shorter time, but this can be argued moving forward.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10