Helpdesk API: every tenant, one gateway

The story

A helpdesk product serves hundreds of companies from one ticket API. Every request passes a gateway that checks the caller's identity and stops one noisy tenant starving the rest. Agents read tickets far more than they write them, and the identity provider behind the gateway has an outage now and then.

The target

• Load: 2,600 requests a second for 8 seconds, 85% of them reads.
• Latency: p99 within 100 ms.
• Budget: $52,000 a month at this load. The gateway's per-request price is most of the bill, so watch where requests go. Half the budget or less earns full cost marks; one and a half times it earns none.
• Faults: three 6-second drills, each with its fault landing 2 seconds in. The ticket API runs twice as slow for 3 seconds, one API instance crashes, and the gateway loses its authorizer. A drill passes when under 1% of requests fail and p99 stays within 200 ms.

What is scored

Throughput 35%, latency 25%, cost 10% and resilience 30%, out of 1,000,000. Every entrant runs the same arrival stream; its seed is published when the week closes so anyone can replay a score.

How to enter

Choose Open in Sandbox. The canvas starts from the palette and starter design this challenge is built on. Build, run it against this scenario, then enter. You get five scored entries this week.