Separate queue for human approvals

Agent 20
AMQPAMQPHTTP/2HTTP/2Partner apps10 req/sPartner apps0 req/sWorker1 vCPU · 1 GBExternal API1 vCPU · 1 GBMessage bro…1 vCPU · 1 GB
AMQPAMQPHTTP/2HTTP/2Partner a…10 req/sPartner a…0 req/sWorker1 vCPU · 1 GBExternal…1 vCPU · 1 GBMessage b…1 vCPU · 1 GB

Turn every goal green.

Traffic
10 req/s · writes only
Limit
Worker answers about 3,300 req/s
Bill
  • Worker4 USD/mo
  • External API4 USD/mo
  • Message broker4 USD/mo
12 of 30 USD/mo

Goals

Not tested yet

How long a message waits before a worker takes it.Work that ran twice.Saved data that was lost later.Time until all the work is done.What the servers and services cost each month.

An agent files 10 safe ticket updates/s. At 0:00 it also proposes 300 refunds, and a person must approve each one, which takes 2 min. Keep safe updates under 5 s in the queue, apply each refund once, lose nothing, and finish by 4:20. The work queue is fixed.

A wait for a person needs its own queueTap or press Space to turn the approval queue on or off

One queue · 60 of 64 workers wait for a person · safe updates wait

Parts you can add: Message broker, Managed queue, Worker, Approval step. At most 4 parts. Budget: 30 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.