Bad batch

Flow 14
HTTP/2SQLHTTP/2Partner apps1,000 req/sAPI server2 vCPU · 2 GBPostgres2 vCPU · 8 GBSearch index2 vCPU · 8 GB
HTTP/2SQLHTTP/2Partner apps1,000 req/sAPI server2 vCPU · 2 GBPostgres2 vCPU · 8 GBSearch index2 vCPU · 8 GB

Turn every goal green.

Traffic
1,000 req/s · writes only
Limit
Postgres answers about 5,000 writes/s
Bill
  • API server8 USD/mo
  • Postgres32 USD/mo
  • Search index32 USD/mo
72 of 120 USD/mo

Goals

Not tested yet

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

A supplier sends 1,000 price updates/s. Ingest writes each one to the catalog database and the search index. At 0:20 a bad batch starts: for 15 s, 40 percent of the prices are in cents, not euros. Keep 0 bad prices in the shop, errors under 0.1 percent and p99 under 2 s.

Each worker adds one network cardDrag or use arrow keys to change the workers

2 workers · 1 TB moves in 1.1 h · 1,000 Mbps per card

Parts you can add: Stream processor, Worker, Message broker. At most 2 parts. Budget: 120 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.