Shifting fraud attacks

Model 20
HTTP/2gRPCPartner apps1,000 req/sAPI server4 vCPU · 4 GBModel (CPU)2 vCPU · 4 GBModel train…1 vCPU · 1 GB
HTTP/2gRPCPartner ap…1,000 req/sAPI server4 vCPU · 4 GBModel (CPU)2 vCPU · 4 GBModel trai…1 vCPU · 1 GB

Keep every goal green in each wave.

Traffic
1,000 req/s · up to 3,000 req/s · reads only
Limit
API server answers about 13,000 req/s
Bill
  • API server16 USD/mo
  • Model (CPU)16 USD/mo
  • Model trainer4 USD/mo
36 of 60 USD/mo

Goals

Not tested yet

The share of time when every target was met.Time from a fault until an alert fires.99 of 100 requests finish faster than this.What the servers and services cost each month.

Survive four 1-minute waves of card payments. Each new wave brings a new fraud pattern, and the last wave has 3 times the traffic. Keep fraud loss plus review cost under 60,000 USD, false alarms under 4 percent, and the targets green for 85 percent of the run.

One change feed keeps serving in stepTap or press Space to change the write paths

Two write paths · 4 of 16 served features differ from training

Parts you can add: Model registry. At most 8 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.