Requirements

Functional Requirements:

• Accept a valid URL in a request
• Return a valid shortened URL
• DO not store the generated URL
• The generated URL can only be accessed by the client that requested it

Non-Functional Requirements:

• Ability to manage high demand and multiple requests
• highly secure
• consistent data

Capacity Estimation

• estimating ability to process 1000 requests per minute

API Design

• REST API
• POST method
• Google SSO Auth with JWT token authentication
• Rate limit to 1 request per client per hour
• /api/v1/urls
• 200 status ok or 500 error

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.

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.

The general design that I have here is that a client sends the request to log in first because you need to be authenticated to use the service, and you're authenticated with Google SSO, which generates a token to use in the request header so when we authenticate a user then we can enable them to send requests to the server through a load balancer.