Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.

Rest API

The api will have a POST endpoint that receives a URL to be shortened from the client. That url will be hashed and stored in a key-value DB like DynamoDB for O(1) lookup with the key being the hash, and the value being the url. Once successfully created, the api will return the shorted url, "<ourdomain>/<hash>" to the client so it can be copied. Our api will have middleware that catches non-post requests like GET "<ourdomain>/<hash>", it will parse out the hash from the incoming request, and perform a redirect on successful lookups. Failed lookups will 404. Since this app is so simple, and yet may require extremely heavy loads, I'd write it in rust for performance. Simple horizontal scaling should work perfectly for performance needs.

Client

The client can be a simple react SPA. React allows for extensibility in the future of the project if we want to add accounts, auth, saved links, and more.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10