Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...

shortenUrl: web sends a request with a url to the server, the server generates a shortUrl for the url, and query database to store them. Once it is stored successfully, return the shortUrl to user.
redirect: web sends a request with a shortUrl to the server, the server first try to fetch the url in cache, if it results in a cache miss, the server will then query the database for the url. If a url is found, returns the url to the web. Otherwise, returns an error code 404.
deleteUrl: Web sends a request with a shortUrl to the server. The server query the database to delete the url under the condition that the owner of the url is the user who sends the request. If a record is deleted, server looks for a match of the shortUrl in the cache. If a match is found, the record is deleted from the cache. The server then returns succeed or failure to the web.
fetchAnalytics: web sends a request with a shorturl to the server. The server fetches the analytics data of the shorturl from the database under the condition that the owner of the shorturl is the user sending the request. The server then sends what's returned by the database to the web.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10