Global config push

Watch 10
RegionRegionRegionSQLSQLSQLUsers1,200 req/sUsers1,200 req/sUsers1,200 req/sAPI server4 vCPU · 4 GBPostgres4 vCPU · 8 GBAPI server4 vCPU · 4 GBPostgres4 vCPU · 8 GBAPI server4 vCPU · 4 GBPostgres4 vCPU · 8 GB
SQLSQLSQLUsersUsersUsersAPI serv…PostgresAPI serv…PostgresAPI serv…Postgres

Fix the board. Turn every goal green.

Traffic
Eu1,200 req/s · 90% readsUs1,200 req/s · 90% reads1 more
Limit
API server answers about 2,000 req/s
Bill
  • API server × 348 USD/mo
  • Postgres × 396 USD/mo
144 of 300 USD/mo

Goals

Not tested yet

The share of requests that fail or get no answer.The share of requests that fail or get no answer.What the servers and services cost each month.

Three regions each serve 1,200 requests/s. At 0:20 a config push reaches every API server at once. All regions fail until a person reverts it at 1:20. A bad change may reach at most 40 percent of servers and must be undone within 30 s. Keep eu and us errors under 0.1 percent.

00:22. Errors climb in eu, us and ap at the same time, 2 s after a config push. Graph: errors by region.

A canary before the whole fleetTap to change the deployment method

Canary · 5% of requests fail for 15 seconds · 750 failed requests

Parts you can add: Alerts. At most 12 parts. Budget: 300 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.