advancedReal System Design Problems

Design a Content Management System (CMS) — versioning, drafts, and publish workflows at scale.

The read-heavy content delivery problem: content versioning, draft-vs-published state management, and how content is cached when it must be invalidated the instant something is published. The cache invalidation strategy on publish — pushing a fresh version out to every edge/cache layer without serving a stale draft — is the most interesting part.

Ready to design this system end to end?

Generate a complete, structured system design answer — requirements, capacity estimation, API design, architecture, database choice, scaling, caching, fault tolerance, security, trade-offs, and more, walked through the way a strong senior engineer would in a real interview.

Sign in to generate a response

Next Step

Continue to What is the difference between sent, delivered, and read ticks in WhatsApp? How is each implemented?← Back to all System Design (HLD) questions