Skip to content

solution.md

Latest commit

 

History

History
21 lines (17 loc) · 1.45 KB

solution.md

File metadata and controls

21 lines (17 loc) · 1.45 KB

Solution.md for Scenario 1 "URL shortener system"

Here is my thought around this challenge: A. Url Processing Module 1. Create StringProcessor class with: i. GenerateShortUrlAndSave method that accepts a string param(eg: www.example.io/someveryveryvery/longlonglong?param=param2) and an expiry_date. ii. A GetUrl method that accepts string param (eg: f2zJZP)

2. The GenerateShortUrlAndSave method should:
    i. Generate a unique string key not more than 10 characters long from  the url param 
    ii. Then persist the url, expiry_date and generated unique key to a datastore (eg: elasticsearch, sqlite, mysql, mssql).
    iii. Return a concatenated string of the service domain(www.trav.ix) and generated unique (f2zJZP) to the caller (eg: www.trav.ix/f2zJZP or www.trav.ix#f2zJZP)

3. The GetUrl method should:
    i. Retrieve the url in the first record where the unique key field matches the method param and not expired from datastore.
4. Expose the Api to compress and get url (for users)

B. Route Module 1. Create an Index action for both Get and Post httpverbs that accept a string param which represents the compressed version original url 2. From the index Action, call the GetUrl method in the Url Processing Module or the public api(in case you are using javascript) to get the original url 3. If the GetUrl method returned a valid url redirect to that url else render an info page