缓存上游并限制速率
保护后端免受失控的模型调用影响。
缓存上游并限制速率 是 CoddyKit 上的免费 MCP Academy 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 MCP Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MCP Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Models Can Hammer Backends
An eager model may call a tool again and again. Without guards, it can overload the database or API behind it. ⚠️
Cache Repeated Reads
A cache stores recent results so an identical request returns instantly instead of hitting the upstream a second time.
Key the Cache by Inputs
Build the cache key from the tool arguments, so the same city or id reuses its stored answer and anything new fetches fresh.
key = ("weather", city)
if key in cache:
return cache[key]Give Entries a TTL
Set a time-to-live so cached data expires. Stale answers get refreshed, keeping results both fast and reasonably current.
Cache Only Safe Reads
Cache idempotent reads, never actions with side effects. You would not want a cached write to silently skip a real change.
Rate-Limit the Calls
A rate limit caps how often a tool may run, so a runaway model cannot fire thousands of requests in a burst.
The Token Bucket Idea
A common scheme is the token bucket: each call spends a token, tokens refill over time, and an empty bucket means wait.
Respect Upstream Limits
Match your limit to the API quota. Staying under its quota avoids 429 responses and keeps your access from being throttled.
Back Off on 429
If an upstream replies 429 Too Many Requests, pause and retry later with backoff instead of pounding it harder.
Bound Concurrency
A semaphore limits how many calls hit the backend at once, smoothing spikes so the upstream is never swamped.
sem = asyncio.Semaphore(5)
async with sem:
...Return a Clear Limit Message
When you do throttle, tell the model plainly that it is rate-limited so it can wait or try a different approach.
Quick Check
What kind of result is safe to cache?
Recap: Cache & Limit
You shielded upstreams with a cache plus rate limits and backoff, keeping backends safe from runaway model calls. 🎯
常见问题解答
「缓存上游并限制速率」课时是免费的吗？
是的 — 「缓存上游并限制速率」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MCP Academy 课程的其余内容，请升级到 CoddyKit PRO。 MCP Academy 课程共包含 4 节课。
「缓存上游并限制速率」这节课中我会学到什么？
保护后端免受失控的模型调用影响。 你通过在浏览器中直接运行的动手代码来练习 MCP Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 MCP Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 MCP Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「缓存上游并限制速率」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 MCP Academy 课中编写并运行代码吗？
能。每节 MCP Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。