Deep health checks

Guard 12
HTTP/2SQLSQLHTTP/2SQLUsers1,800 req/sLoad balanc…1 vCPU · 1 GBNode API1 vCPU · 1 GBConnection…0.5 vCPU · 1 GBNode API1 vCPU · 1 GBConnection…0.5 vCPU · 1 GBNode API1 vCPU · 1 GBConnection…0.5 vCPU · 1 GBPostgres4 vCPU · 8 GB
HTTP/2SQLSQLHTTP/2SQLSQLHTTP/2SQLSQLUsers1,800 req/sLoad balan…Node APIConnection…Node APIConnection…Node APIConnection…Postgres

Fix the board. Turn every goal green.

Traffic
1,800 req/s · 80% reads
Limit
Node API answers about 1,000 req/s
Bill
  • Load balancer (L7)4 USD/mo
  • Node API × 312 USD/mo
  • Connection pooler × 312 USD/mo
  • Postgres32 USD/mo
60 of 80 USD/mo

Goals

Not tested yet

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.

At 0:20 one third of orders started to fail. All three API servers still pass their health checks, and the balancer still sends each one a third of the traffic. Keep errors under 1 percent and p99 under 100 ms. You have 3 edits.

0:20. Order errors jump to 33 percent. The balancer shows 3 of 3 API servers healthy. Graph: errors by API server.