Reads go back in time

Quorum 13
SQLUsers800 req/sPostgres1 vCPU · 2 GB × 3
SQLUsers800 req/sPostgres1 vCPU · 2 GB × 3

Fix the board. Turn every goal green.

Traffic
800 req/s · 50% reads
Limit
Postgres answers about 45,000 reads/s
Bill
  • Postgres24 USD/mo
24 of 30 USD/mo

Goals

Not tested yet

Reads that returned old data.The share of requests that get a correct answer.99 of 100 requests finish faster than this.What the servers and services cost each month.

At 0:20 the primary crashes and a follower takes over. At 0:26 the old primary returns and replays 2,400 missed writes. Readers see a comment, reload, and it is gone. Keep stale reads under 30 and availability above 98 percent. Budget: 30 USD/month.

0:26. A comment vanished on reload. Graph: stale reads jump while the returned copy replays 2,400 writes.