<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Caching on API Course</title>
    <link>https://apicourse.com/tags/caching/</link>
    <description>Recent content in Caching on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Caching for APIs: Cache-Control, ETags, and Conditional Requests</title>
      <link>https://apicourse.com/http-caching-for-apis-cache-control-etags-and-conditional-requests/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/http-caching-for-apis-cache-control-etags-and-conditional-requests/</guid>
      <description>&lt;p&gt;Caching is one of the highest-leverage performance improvements available to an API, and one of the least consistently implemented. A response that is cached at the right layer — in a CDN, a reverse proxy, or the client itself — eliminates a server round trip entirely. At scale, that elimination compounds: fewer database queries, lower infrastructure cost, faster responses for every consumer. The HTTP specification provides a complete, standardized caching system. Most APIs use it only partially, leaving significant headroom unrealized.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
