<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>N&#43;1 on API Course</title>
    <link>https://apicourse.com/tags/n&#43;1/</link>
    <description>Recent content in N&#43;1 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/n+1/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Performance Optimization: Compression, Connection Pooling, and N&#43;1 Queries</title>
      <link>https://apicourse.com/api-performance-optimization-compression-connection-pooling-and-n-1-queries/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-performance-optimization-compression-connection-pooling-and-n-1-queries/</guid>
      <description>&lt;p&gt;API performance problems fall into two categories: the ones that appear immediately during development and are fixed before they matter, and the ones that are invisible during development and catastrophic at production scale. The second category is where the interesting work is. Understanding where APIs slow down under load — and the specific techniques that address each cause — is the difference between an API that performs at scale and one that requires emergency remediation after launch.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
