Stolen token

Lock 02
HTTP/2HTTP/2SQLHTTP/2SQLHTTP/2HTTP/2SQLUsers2,000 req/sLoad balanc…1 vCPU · 1 GBPostgres0.1 vCPU · 1 GBAPI server0.5 vCPU · 1 GBLocal cache0.1 vCPU · 0.5 GBAPI server0.5 vCPU · 1 GBLocal cache0.1 vCPU · 0.5 GBAPI server0.5 vCPU · 1 GBLocal cache0.1 vCPU · 0.5 GB
HTTP/2HTTP/2SQLHTTP/2SQLHTTP/2HTTP/2SQLUsersLoad bal…PostgresAPI serv…Local ca…API serv…Local ca…API serv…Local ca…

Fix the board. Turn every goal green.

Traffic
2,000 req/s · reads only
Limit
Postgres answers about 1,500 reads/s
Bill
  • Load balancer (L7)4 USD/mo
  • Postgres4 USD/mo
  • API server × 312 USD/mo
  • Local cache × 36 USD/mo
26 of 60 USD/mo

Goals

Not tested yet

How old the data is when a reader gets it.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.

Each API instance checks a session token once, then trusts it for 24 hours. A revoked session keeps working on the other instances. A revoked token must stop within 5 minutes. Keep p99 under 80 ms. You have 5 edits.

0:05. A user reset the password after a phishing email. The stolen token still opens the account. Graph: freshness keeps rising.

Parts you can add: Managed pub/sub, Managed queue, Local cache, Redis cache. At most 12 parts. Budget: 60 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.