Requirements

Functional Requirements:

• Create a short URL for a given long URL.
• Return the long URL associated with a given short URL.

Non-Functional Requirements:

• List the key non-functional requirements (eg low latency, scalability, reliability, etc.)...
• speed-system must lookup request and return values fast
• serverless-because as new aliases are created size of dictionary/database must be increased dynamically
• check if alias exists send error

API Design

Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...

• CheckIfExists function: check sif alias for a particular url already exists.

IF alias in ( Select alias from table where url = url) return 1 else 0

• CreateAlias api: if http request=get: render form with fileds for intake of url and alias. submit button

if http request=post:

-check if valid input else throw error

-CheckIfExists: if yes return error under form field 'alias already exits. if no: insert into table (url,alias) values (url given and alias given)

• AccesURL: take in shortened url, after domain name extract all text. that is the alis.lookup table for alias and return url. select from table where alias=given alias. if alias empty send error-alias not found

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

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.

scaling of database- should use some serverless architecture so they can scale up as new aliases are created