How to Implement a URL Shortener as a Service: A Step-by-Step Guide
A URL shortener service takes a long URL and returns a short alias that redirects users to the original link. Building one involves a few core components: a unique ID generator, a database, an API, and a redirection handler. This tutorial covers the essential steps to create a scalable shortener service.
You will learn how to design the database schema, generate short codes safely, and expose RESTful endpoints for creation and retrieval. The service should be stateless and support high read throughput.
1. Database Schema & Code Generation
Store the mapping in a simple table with columns: id (auto-increment), short_code (unique), original_url (text), created_at (timestamp). Generate a unique short code, e.g., using base62 (a–z, A–Z, 0–9). Convert the auto-increment ID to base62 for collision‑free codes, or use a random string with duplicates check.
Example (pseudo‑code):
function shortCode(id):
chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"
code = ""
while id > 0:
code = chars[id % 62] + code
id = id // 62
return code
2. API Design
Build two endpoints for a RESTful service:
- POST /shorten – accepts
{ "url": "..." }, returns{ "short_url": "http://your.domain/abc123" }. Validate the URL, generate the code, store it, and respond. - GET /:code – looks up the code, fetches the original URL from the database, and returns a 301 (permanent) or 302 (temporary) redirect response.
3. Redirection Logic
When a request arrives for /abc123, the service:
- Extract the short code from the path.
- Query the database for the matching record.
- If found, set HTTP status 301 and the
Locationheader to the original URL. - If not found, return a 404 error.
Implement caching (e.g., Redis) for the most popular codes to reduce database load.
4. Scaling Considerations
To handle millions of redirects, add a cache layer (TTL of a few hours), use a read‑replica for the database, and deploy behind a load balancer. For higher throughput, pre‑generate batches of short codes and serve them from a pool to avoid lock contention.
Key Performance Tips:
- Use an in‑memory cache (Redis/Memcached) for lookups.
- Rate‑limit the creation API to prevent abuse.
- Store the full URL in a column with a UNIQUE index on
short_code.
Conclusion
Implementing a URL shortener as a service is a great project for learning backend fundamentals. Focus on a clean database design, efficient code generation, and a fast redirection layer. With caching and horizontal scaling, your service can handle millions of requests reliably.