Requirements

Functional Requirements:

• User should be able to put the long URL and get a short URL in response
• Anyone hitting the shortURL should be redirected to the actual
  • Now there 2 reditects
    • Temporary -> Benefit is that we can track and keep telemetry data
    • Permanent -> No tracking

Non-Functional Requirements:

• System has to be highly available
• Highly consistent
• Low Latency

Capacity Estimation

API Design

Define the APIs expected from the system:-

• PUT /v1/make-tiny/
  • JSON Body - { url , maxExpiryDate:optional }
• GET /v1/redirect/id=xyz , where xyz is the key of the search to which the user needs to be redirected to

High-Level Design

So the idea is that we have a load answer and it's an application not well answer because. At the low balance available itself he will decide where the request will go because in the back end we have to services we have a service which will add URL and IT act like a data layer it will create new mapping. You know it will create a key and it will happen to the long URL store it in the database in parallel to that it will do new it will set one detail and event that it will not put it in the right replica of the cache as well now the right replica will sing with the read replica reader because if I go head and keep updating the replica right then that operation is very where as if I just update and updates other read replica that operation is much fast so that's why we are writing to the reader. Absorb that change and when the consumer comes in they will hit the gate you are all option.

Database Design

Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...

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.

I would use base64 strings to create the tinly URL based on the scale which you mentioned