Design a URL shortener system architecture
About the framework
The URL shortener example shows a browser, load balancer, API service, Redis cache, Postgres URL map, ID generator, analytics service, CDN, and Kafka queue. Eight arrows connect these nine components. A separate metrics box lists 100 million daily redirects, p99 latency below 50 milliseconds, and 99.99% uptime as sample targets, not measured results.
The API connects to the cache and database. Other links run from the cache through ID generation to the CDN, and from the database through analytics to Kafka. That layout leaves the actual order of link creation, cache lookup, redirect delivery, and event publication unresolved.
Adapt the drawing by separating create-link and redirect requests. Define where IDs are allocated, how cache misses reach storage, and when click events are emitted. Use your traffic assumptions to review the targets rather than treating the diagram as evidence that they are achievable.
What's included
URL Shortener System Design
✦ Free preview · Sign in to use
Frequently asked questions
No. That number is a label in the example metrics box. Capacity planning and load testing would be separate work based on a defined workload.
The drawing connects the cache to the ID generator and then the CDN. It does not spell out how a create request allocates an ID and stores the URL mapping; ask for that path explicitly.
Neither is shown. Add expiration, invalid-link responses, and the checks required by your service before using the diagram as an implementation reference.
Free to start. No credit card required.