Request flood waves

Lock 07
HTTP/2HTTP/2HTTP/2SQLUsers0 req/sUsers800 req/sUsers0 req/sLoad balanc…1 vCPU · 1 GBNode API2 vCPU · 2 GBPostgres1 vCPU · 2 GB
HTTP/2HTTP/2HTTP/2HTTP/2SQLUsers0 req/sUsers800 req/sUsers0 req/sLoad bal…Node APIPostgres

Keep every goal green in each wave.

Traffic
Visitors800 req/s · 90% readsPage flood0 req/s · up to 20,000 req/s · reads only2 more
Limit
Node API answers about 2,000 req/s
Bill
  • Load balancer (L7)4 USD/mo
  • Node API8 USD/mo
  • Postgres8 USD/mo
20 of 22 USD/mo

Goals

Not tested yet

The share of time when every target was met.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.

Four waves hit the site. From 0:40, 300 bot addresses flood a page. From 1:20 they also flood sign-in. From 2:00, 40,000 more addresses join at a slow rate. Keep visitor p99 under 300 ms for 90 percent of the run. You get 2 USD/mo more at each wave.

A reader with no tools stops page ordersTap or press Space to add or remove the reader

Separate reader · 0 of 100 attacks reach a tool

Parts you can add: Rate limiter, Node API, Load balancer (L7). At most 10 parts. Budget: 22 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.