URL Shortener Design

A URL shortener service transforms long, often complex URLs into concise, readable links. This is crucial for sharing on platforms with character limits, improving user experience, and tracking link engagement.

The Redirect Server

At its core, a URL shortener operates as a redirect server. When a user accesses a short URL, the server performs a lookup, finding the corresponding original long URL and then issuing a redirect. This functionality relies on a simple key-value mapping where the short ID is the key and the long URL is the value.

The Write Path: Shortening a URL

When a user submits a long URL to be shortened, the client sends a POST request to the server. The server generates a unique short ID, stores this ID along with the original long URL in a database, and then returns the newly created short ID to the client. This process effectively creates the mapping.

The Read Path: Accessing a Short URL

When a browser requests a short URL (e.g., `bit.ly/3xY7z`), the server receives a GET request for the short ID. It queries its database for the associated long URL. Once found, the server responds with an HTTP 301 Redirect status code, instructing the browser to navigate to the original long URL.

Generating Compact Short IDs with Base62

To create short, yet unique, IDs, URL shorteners often use Base62 encoding. This character set includes lowercase letters (a-z), uppercase letters (A-Z), and digits (0-9), totaling 62 unique characters. With a short ID length of just 7 characters, Base62 can generate `62^7` unique combinations, providing capacity for over 3.5 trillion unique short URLs. This allows for extremely compact IDs that pack significant data into fewer positions.

Optimizing Performance with Caching

To handle high traffic efficiently, a caching layer is essential. Popular short URLs are frequently accessed, so serving them directly from a fast in-memory cache, like Redis, significantly reduces the load on the primary database. When a request for a short ID comes in, the server first checks the cache. If the mapping is found (a cache hit), it's returned immediately. If not (a cache miss), the server fetches the long URL from the persistent database, stores it in the cache for future requests, and then issues the redirect.

Key Takeaways

• URL shorteners map short IDs to long URLs for redirection.
• The write path generates and stores these mappings.
• The read path retrieves mappings and issues 301 redirects.
• Base62 encoding creates compact, high-capacity short IDs.
• Caching popular links (e.g., with Redis) is crucial for performance.