Architecture Simulator

The Viral Deck

Users can publish a design as a public page. Most are read by nobody. One of them is a conference keynote that has just been linked from everywhere, and it is being opened about forty thousand times a minute by people who will never log in. The content changed once, this morning, and will not change again. The same service also serves the editor, where people are working on documents they very much expect to be up to date. Your database is the one that holds everything. If public traffic takes it down, it takes the editor with it. Somebody will ask, afterwards, why the page could not simply have been served from cache. Make sure the answer is that it was.

Must meet

p99 latency: ≤ 300ms
Availability: ≥ 99.95%
Budget: ≤ $2500/mo
Durability: durable
Consistency: eventual

The system does

·Public, crawlable pages
·Accounts and login
·Reporting and exports

Components

Drag onto the canvas, or tap one and then tap where it goes. Not everything here belongs in every design — picking the wrong component is part of the exercise.

TrafficNormal publishing traffic · 500 rps peak

p99 0msavail 0.00%cost/mo at peak $0