What it does
Dub is a link management platform with branded links, redirect rules, and analytics. Its application combines transactional link data with high-volume click events.
Why it’s interesting
Redirects need low latency while analytics needs throughput. Separating the redirect path from event analysis is a useful architecture study.
Real-world use case
Route a campaign link to different destinations by device and review click attribution.
What I can learn
- 01
Edge redirects and caching
Trace how a short-link request resolves its destination close to the edge and how caching reduces redirect latency.
- 02
Transactional data versus analytical event storage
Understand why link configuration belongs in transactional storage while high-volume click events go to analytical storage.
- 03
Tenant-owned domains and DNS validation
Learn how a platform verifies customer DNS records before routing traffic for a tenant-owned link domain.
One thing to explore
Redirect middleware and analytics pipeline
Follow the apps/web implementation and connect it to the concepts above.
Explore the source (opens in a new tab)10-Minute Challenge
Explore the monorepo and redirect path
Before you start: A browser and Git. Full local startup needs the services and environment configuration listed in the repository guide.
- Clone the repository and read its current development setup before installing dependencies.
- Inspect the root workspace configuration and locate the redirect handler.
- Trace how a click event is recorded without slowing the redirect response.
git clone https://github.com/dubinc/dub.gitcd dub