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.

components:

creator

consumer

url shortener service

redirect service

api-gateway for authentication, authorization, rate limiting and request routing

for secure connections, https protocols

load balancing algo: least connections

CDN for lower latency.

to ensure uniques identifiers i'll store a counter in a db (redis)centrally accessible to all servers for url-shortening service and hash it for security.

then keep incrementing a counter on new url request.(even if there is any failure , we'll have redis cluster with replicas for failover).

we'll do exponential retries, with a jitter added.

if there is any failure with one of the services, we'll use circuit breaker to avoid cascading failures

separate pool resources i.e. bulkhead pattern to avoid one service impacting another.

to avoid race condition i'll use locking on db

cache

db for long-url to short-url mapping and other details

for redirect service, we'll first check if long url for that short url is already prsent in CDN, if yes we return data from there and redirect to right place

otherwise, CDN pulls the data from orginal server, updates itself and then returns the requested url for redirect

if redirect fails we analyze the lgos using analytics service and use it to improve the services

for caching we will use redis cache and cache details like short url to long url mapping, and if any alias is specified

in db we store details like user info, short url, long url, alias if provided.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10