Link-in-bio service inspired by Linktree: each creator has a public page of links that is served from the edge, edits are saved to a database, and click analytics are counted in the background.
See why building a page from the database on every visit does not scale.
What was missing: A public page should not be rebuilt from the database on every visit.
Why that's risky: A famous creator sends thousands of visitors per second to one page, all running the same query.
What gets added: One server that reads a creator's links from the database on every visit and saves edits.
Trade-offs: Always current, but slow under load.
Separate viewing from editing and serve pages from memory.
What was missing: Viewing and editing share one path.
Why that's risky: An edit can take a moment to show in the cache.
What gets added: A page service reading from a cache keyed by handle, an editor service and a profile database as source of truth.
Trade-offs: Pages are a few seconds stale after an edit.
Serve public pages from the edge so a famous creator never overloads us.
What was missing: A famous creator's spike still reaches our servers.
Why that's risky: An edited page can show the old links until its edge copy expires or is purged, and a click served entirely from the edge would never be seen by us.
What gets added: A CDN serves each public page from the edge.
Trade-offs: Page views are cached at the edge, but clicks go through our redirect endpoint so they can be counted; purge on edit keeps pages fresh.
Count clicks in the background and protect editing.
What was missing: Clicks are not counted and bots can create spam pages.
Why that's risky: Counting each click with a database write at 10K clicks/s would crush the database.
What gets added: The page service records each link click as an event on a queue before redirecting; workers count clicks per link in batches. A rate limiter on edits and page creation, and monitoring.
Trade-offs: Click counts lag by up to a minute in exchange for batched writes.
You're in the middle of an interview session. Leaving now will end your current attempt.
Explore concept overviews, real-system examples, key tradeoffs, and interview talking points for each roadmap section.
You've conquered this phase. These are the skills you now own: