Blogging platform inspired by Medium and Ghost: authors publish posts, readers get pages from a cache and the CDN edge, and rendering and follower updates happen in the background.
See why building a page from the database on every request does not scale.
What was missing: A post should not be rebuilt from the database for every reader.
Why that's risky: A viral post means thousands of identical page builds per second, all hitting the same database rows.
What gets added: One server that reads a post from the database and builds the page on every request, and saves new posts.
Trade-offs: Simple, and always shows the latest edit.
Separate reading from publishing and serve posts from memory.
What was missing: Reading and publishing share one path and every page hits the database.
Why that's risky: After an edit the cache can show the old version until it is refreshed or invalidated.
What gets added: A post service reading from a cache keyed by post id, a separate publish service that writes to the post database.
Trade-offs: Readers may see a post a few seconds old, which is fine for articles.
Serve popular posts from the edge so a viral post never reaches our servers.
What was missing: Every read still reaches our servers, and a viral post is read from one origin.
Why that's risky: An edge copy of an edited post stays visible until it expires or is purged.
What gets added: A CDN serves the rendered page from the edge.
Trade-offs: A longer edge TTL helps viral posts but delays edits; purge-on-publish fixes that.
Render pages and update follower feeds in the background.
What was missing: Pages are rebuilt on demand, follower feeds are not updated and spam can flood publishing.
Why that's risky: If an author with a million followers published inside the request, publishing would stall.
What gets added: A publish queue with render workers that pre-render the page, purge the old copy and push the post to follower feeds, plus a rate limiter and monitoring.
Trade-offs: Fan-out on write makes follower reads cheap but costs work per follower; huge accounts are usually fanned out lazily.
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: