<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Efficiency on API Course</title>
    <link>https://apicourse.com/tags/efficiency/</link>
    <description>Recent content in Efficiency 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/efficiency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Batch Operations in APIs: Designing for Bulk Without Breaking Everything</title>
      <link>https://apicourse.com/batch-operations-in-apis-designing-for-bulk-without-breaking-everything/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/batch-operations-in-apis-designing-for-bulk-without-breaking-everything/</guid>
      <description>&lt;p&gt;The standard REST pattern is one resource per request. Create one user, update one order, fetch one product. This works until an integrator needs to create ten thousand users, update five hundred orders, or sync an entire product catalog. Making ten thousand individual API calls is slow, expensive in terms of rate limit quota, and brittle — a network failure on request 7,432 leaves the integrator with a partially completed operation and no clean recovery path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
