How to Build a Scalable Short URL Service: Algorithms, Use Cases, and Code

1. Introduction

When preparing interview questions, a common challenge is how to convert a long URL into a short one and enable mutual conversion. Short URLs compress long addresses into a compact form that redirects to the original link, making them easier to remember and suitable for character‑limited platforms like micro‑blogs and QR codes.

2. Short URL Use Cases

2.1 Micro‑blogging (e.g., Sina Weibo) – Weibo limits posts to 140 characters, so long links would consume most of the space. The platform automatically shortens URLs (e.g., https://t.cn/RuPKzRW) to preserve space and improve user experience.

2.2 QR Codes – Short URLs can be turned into QR codes, reducing the amount of data a user must scan and enabling cross‑platform data transfer. QR codes also support richer metadata such as product origin, production date, and traceability information.

3. Benefits of Short URLs

Save length for easier social sharing, especially when URLs contain Chinese characters or special symbols.

Facilitate management and moderation of links (e.g., filtering malicious or advertising URLs).

Enable backend analytics such as click counts and geographic distribution.

Bypass keyword or domain blocking and hide the original address, useful for paid promotion.

Free up character space in platforms with strict limits, like micro‑blogs or SMS.

4. Short URL Service Providers

Sina: http://sina.lt/ Baidu: http://dwz.cn/ 0x3: http://0x3.me/ MRW: http://mrw.so/ When choosing a provider, ensure long‑term reliability; otherwise previously generated short links may break.

5. How to Generate Short URLs

Common approaches include mapping tables, hash functions, and signatures, but many are unsuitable for large‑scale scenarios. A practical method uses an incremental “ticket dispenser” (ID generator) combined with base‑62 encoding.

6. Design of a Short URL Generator

(1) Maintain a counter starting at 0; each request increments the counter and converts the value to base‑62 (a‑z, A‑Z, 0‑9). For example, 0 → a, 1 → b, 10000 → sBc. (2) Concatenate the domain (e.g., t.cn/) with the base‑62 string to form the short link. (3) Store the mapping short → long in a key‑value store (Redis, Memcached). When a user accesses the short link, look up the original URL and issue a 302 redirect.

7. Redirection Flow

User requests http://t.cn/RuPKzRW.

Server retrieves the original URL (e.g., https://blog.csdn.net/.../79863301) from KV storage.

Server responds with HTTP 302 and Location header pointing to the original URL.

Browser follows the redirect and loads the long page.

8. Optimizing the Ticket Dispenser

Algorithmic Optimizations – Avoid generating multiple short links for the same long URL by checking an existing mapping table first (though this may be slower). A more efficient approach uses an LRU cache to store recent mappings, trading space for speed.

Scalability & High Availability – A single‑node service becomes a bottleneck and a single point of failure. Deploy a cluster with sharding: each instance handles a specific range of IDs (e.g., modulo 10 for ten nodes). The mapping storage can also be sharded, requiring a lookup service to locate the correct node.

9. Sample Implementation

A minimal open‑source project urlshorter demonstrates a random‑based short URL generator (note: it does not use the ticket dispenser method and may suffer from collisions). The project is hosted at:

https://gitee.com/tinyframework/urlshorter

10. Conclusion

We have covered what short URLs are, their advantages, practical generation methods, scalability considerations, and provided a reference implementation, giving you a solid foundation to design and deploy your own URL shortening service.