Llm Gateway Cost And Caching easy
A provider capacity shortage halves your available throughput. Free and paid traffic share one FIFO queue at the gateway, and paid customers are now timing out. What should the gateway do?
- A Retry every failed request immediately so the queue drains faster during the shortage.
- B Increase the queue length so more requests from all tiers wait instead of failing.
- C Route all traffic to the cheapest model so the reduced capacity serves more calls.
- D Add priority tiers so paid traffic is served first and free traffic is delayed or shed.
Answer: D. Add priority tiers so paid traffic is served first and free traffic is delayed or shed.
**Priority tiers protect paid traffic** during shortages by deliberately degrading free users, trading fairness for revenue protection. A longer FIFO queue just makes everyone wait longer, paid users included. Immediate retries add load and worsen the shortage, and a cheaper model only helps if its quality floor is acceptable for every feature.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your primary LLM provider is fully down for an hour, and no tested fallback exists for your agent feature. The product also has an FAQ answer feature backed by a semantic cache. What is the best degradation mode?
- Your gateway applies one 5-second timeout to all LLM calls. Classification calls work fine, but long streamed answers are frequently cut off. What is the best fix?
- A multi-tenant B2B support assistant answers questions using each customer's private knowledge base. To raise the semantic cache hit rate from 22% to 35%, an engineer proposes one shared cache across all tenants. What is the main problem?
- During a provider brownout returning 429 and 503 errors, the client SDK retries 3 times and the gateway also retries 3 times, both immediately. Provider load spikes, and the bill grows from partially streamed responses. What should you change?
- Finance asks for LLM spend broken down by tenant and by product feature. Today the gateway only sees the total on the provider's monthly invoice. What should you do?
- A retail assistant uses a semantic cache. Weeks after a store changed its holiday hours, users still receive the old hours from cached answers. What is the right fix?