1 min lesson
What is and isn't cacheable for a developer tool
Pick two rows from the table in "What is and isn't cacheable for a developer tool" and explain the choice each one supports.
Step 1 of 2
What is and isn't cacheable for a developer toolthe CDN is only as useful as your cache hit ratio
A CDN earns its keep on static, shared, immutable bytes. The trap for an AI dev tool is that the high-value traffic is the least cacheable: a user's prompt, their repo context and a streamed model completion are all personalized and one-shot. Be specific about the split.
- Traffic
- App binaries, updater deltas, fonts, marketing site
- Cacheable?
- Yes, aggressively
- Why / how
- Immutable, content-hashed; long TTLs, cache by URL
- Traffic
- Public docs, OG images, static API schemas
- Cacheable?
- Yes
- Why / how
- Shared across users; revalidate on deploy
- Traffic
- Auth'd API responses (settings, entitlements)
- Cacheable?
- Rarely
- Why / how
- Per-user; only with short private TTLs and a vary on identity
- Traffic
- Prompts, retrieval results, model completions
- Cacheable?
- No
- Why / how
- Personalized, one-shot, often streamed token by token
| Traffic | Cacheable? | Why / how |
|---|---|---|
| App binaries, updater deltas, fonts, marketing site | Yes, aggressively | Immutable, content-hashed; long TTLs, cache by URL |
| Public docs, OG images, static API schemas | Yes | Shared across users; revalidate on deploy |
| Auth'd API responses (settings, entitlements) | Rarely | Per-user; only with short private TTLs and a vary on identity |
| Prompts, retrieval results, model completions | No | Personalized, one-shot, often streamed token by token |
For Cursor, the edge wins on delivery and protection more than on caching the hot path.