Indie Hacker Mobile Apps · 课时

API 速率限制与缓存策略

通过实施速率限制阻止滥用,并使用缓存层减少重复工作、加快响应速度,从而保护后端并降低成本。

第 4 / 4 课13 个步骤

API 速率限制与缓存策略 是 CoddyKit 上的免费 Indie Hacker Mobile Apps 课时。 这是第 4 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Indie Hacker Mobile Apps 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Indie Hacker Mobile Apps 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Why Limit and Cache

As your app grows, two problems appear: abusive or runaway clients hammering your API, and the same expensive work repeated needlessly. Rate limiting and caching solve both.

Together they protect uptime and slash costs.

What Is Rate Limiting?

Rate limiting caps how many requests a client can make in a window — for example 100 requests per minute. Beyond that, requests are rejected or delayed.

It defends against abuse, bugs, and accidental loops.

The Token Bucket

A common algorithm is the token bucket: each request consumes a token; tokens refill at a steady rate. When the bucket is empty, requests are throttled.

let tokens = 5;
function allowRequest() {
  if (tokens > 0) { tokens--; return true; }
  return false;
}
console.log(allowRequest());
console.log(allowRequest());

Communicating Limits

Good APIs return headers like X-RateLimit-Remaining and a 429 Too Many Requests status with a Retry-After hint.

This lets well-behaved clients back off gracefully.

What Is Caching?

Caching stores the result of expensive work so repeat requests return instantly without recomputing or re-fetching.

A cache hit saves database load, compute, and time.

Cache Keys and TTL

Each cached entry has a key identifying the request and a TTL (time to live) after which it expires and is refreshed.

const cache = new Map();
function setCache(key, value, ttlMs) {
  cache.set(key, { value, expires: Date.now() + ttlMs });
}
setCache('user:1', { name: 'Alice' }, 60000);
console.log(cache.get('user:1'));

Cache Layers

Caching happens at multiple levels:

  • Client: in-app cache
  • CDN: at the edge near users
  • Server: in-memory or Redis

Each layer cuts work from the one below it.

Cache Invalidation

The hard part: stale data. When the underlying data changes, the cache must be invalidated or it serves outdated results.

Strategies include short TTLs, event-based invalidation, and versioned keys.

What Not to Cache

Avoid caching:

  • Highly personalized or sensitive data without scoping by user
  • Rapidly changing values where staleness misleads

Cache what is read often and changes rarely.

Combining the Two

Rate limiting and caching reinforce each other. Caching reduces how often you hit the limit, and limits protect uncached, expensive endpoints from abuse.

Apply both per endpoint based on cost and sensitivity.

A Protection Checklist

Before scaling:

  • Rate limit per user and per IP
  • Return 429 with Retry-After
  • Cache hot, slow-changing reads with sensible TTLs
  • Plan invalidation up front
  • Never cache sensitive data unscoped

Resilient and cheap to run.

Quick Check

Test your rate limiting and caching knowledge.

Recap

You learned to protect and speed up your backend:

  • Rate limiting caps requests and defends against abuse
  • Token bucket is a common algorithm; return 429 with Retry-After
  • Caching stores expensive results across client, CDN, and server
  • Use TTLs and plan invalidation to avoid stale data
  • Combine both per endpoint by cost and sensitivity

Resilient, fast, and cheap to operate.

免费开始

用 AI 导师学习 Indie Hacker Mobile Apps — 免费

在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。

课程
12
课程
48

常见问题解答

「API 速率限制与缓存策略」课时是免费的吗?

是的 — 「API 速率限制与缓存策略」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Indie Hacker Mobile Apps 课程的其余内容,请升级到 CoddyKit PRO。 Indie Hacker Mobile Apps 课程共包含 4 节课。

「API 速率限制与缓存策略」这节课中我会学到什么?

通过实施速率限制阻止滥用,并使用缓存层减少重复工作、加快响应速度,从而保护后端并降低成本。 你通过在浏览器中直接运行的动手代码来练习 Indie Hacker Mobile Apps,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Indie Hacker Mobile Apps 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Indie Hacker Mobile Apps 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 4 节课,共 4 节。

「API 速率限制与缓存策略」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Indie Hacker Mobile Apps 课中编写并运行代码吗?

能。每节 Indie Hacker Mobile Apps 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 优化 BaaS 性能
  2. 自定义后端集成
  3. 移动应用安全最佳实践
  4. API 速率限制与缓存策略
← 返回 Indie Hacker Mobile Apps