Sortable ids without a counter

Scale 22
RegionRegionRegionHTTP/2HTTP/2HTTP/2HTTP/2HTTP/2Users33,334 req/sAPI server3 vCPU · 1 GBUsers33,334 req/sAPI server3 vCPU · 1 GBUsers33,334 req/sAPI server3 vCPU · 1 GBKey-value…8 vCPU · 1 GB
HTTP/2HTTP/2HTTP/2UsersAPI s…UsersAPI s…UsersAPI s…Key-v…

Turn every goal green.

Traffic
Ids eu33,334 req/s · writes onlyIds us33,334 req/s · writes only1 more
Limit
API server answers about 60,000 req/s
Bill
  • API server × 336 USD/mo
  • Key-value store32 USD/mo
68 of 80 USD/mo

Goals

Not tested yet

99 of 100 requests finish faster than this.The share of requests that fail or get no answer.What the servers and services cost each month.

Apps in 3 regions need 100,000 new ids/s. Ids must be unique and sort by creation time to within 1 s. Each id needs p99 under 20 ms, under 0.1 percent errors, at most 80 USD/mo. The clock in one region runs 300 ms ahead.

A lease with a fencing tokenTap to turn the fencing tokens on or off

Fencing tokens · lease 30 s · late write with token 33: rejected

Parts you can add: Key-value store, Postgres, API server. At most 7 parts. Budget: 80 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.