Problems / AI products, hard
A shopping agent checks out through an external payment API that is down from 15 s to 30 s.
Free to open. Runs in your browser, no sign-up.
Success ≥ 95% of tasks, p99 ≤ 90 s.
3 requests a second for 45 seconds: 100% task (writes).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls Agent API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| Agent APIApp service | Load balancer forwards to it.Calls Agent orchestrator.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 500 slots · timeout 180 s |
| Agent orchestratorAgent orchestrator | Agent API calls it.Calls Model, Payment API.An agent loops: think, call a tool, read the result, repeat until done. | 400 slots · 3 steps |
| ModelLLM endpoint | Agent orchestrator calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second. | 300 streams |
| Payment APIExternal API (mock) | Agent orchestrator calls it.Third-party APIs have their own rate limits and outages that you cannot fix. | 400 slots · 60,000 calls/min |
Try it first. Open one hint at a time if you get stuck.
The agent is fine; the provider isn’t.
Find the red card first, then its capacity: slots ÷ seconds per request.
Add a fallback payment provider.