simulations

A feed that everybody reads and almost nobody writes

You serve a public activity feed. Reads outnumber writes a hundred to one, every read hits the same database, and the database is the most expensive thing you own.

The store is a single relational instance. You can put things in front of it and you can change how it is asked, but you cannot make it faster.

Launch week

stage 1 of 3

Sixty reads a second against sixty distinct feeds. Half a second at the tail, and under twenty cents.

load
60/s
writes
1%

Before anything runs: which promise gives way first, and what is the mechanism?

Nothing runs until this is written. Afterwards it runs on every change.
GET /feedqueryReaderscustomWeb tiercustomFeed databasecustom

What has to hold

The slowest read in a hundred is under 0.5s

Every number appears here, on every change.

Add a component

rent $0.0019 over the run
edge
compute
data
async
coordination
outside