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...

Client: Initiates requests to either shorten a URL or request a redirect.
API Gateway: Manages client requests and directs them to the appropriate service (Shortening or Mapping). This also provides DDoS protection and can do TLS termination.
Shortening Service: Handles URL generation requests. It creates mappings of long URLs to short URLs in the database, and updates an in-memory or distributed cache for quick access.
Mapping Service: Handles redirect requests. It first checks the cache for the short URL mapping. If not found, it will query the database. The service responds with the redirection URL.
Cache: A key-value store, like Redis, provides fast access to frequently used mappings to speed up redirection requests.
Database: A scalable NoSQL database like DynamoDB stores all mappings in a more persistent form, ensuring data consistency and availability.
Service Response: Directs the output of cache/database lookups back to the client.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10