First Come, First Severed

Bob's product API serves four customers a second, and four was always enough. Then a competitor's scraper found the endpoint: 500 requests a second, none of them buying anything. Postgres serves everyone in the order they show up, so your paying customers are now stuck behind a bot photocopying the price list, and the database is buckling. The Job: Keep the real customers served and inside the latency SLA while the flood is on. The catch: You don't win by turning so many people away that the store may as well be closed. Say no to the bots. Not to the buyers.

Free to play, no account needed. A deterministic engine grades your design against this scenario's SLA - error rate, latency, and cost.