<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Apisix on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/apisix/</link>
    <description>Recent content in Apisix on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/apisix/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted API Versioning Management: Kong vs APISIX vs Tyk (2026 Guide)</title>
      <link>https://www.pistack.xyz/posts/2026-05-21-self-hosted-api-versioning-management-kong-apisix-tyk-guide/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-21-self-hosted-api-versioning-management-kong-apisix-tyk-guide/</guid>
      <description>&lt;p&gt;Managing multiple API versions is one of the hardest challenges for growing engineering teams. When you break backward compatibility, you need a clean migration path — and that means running v1, v2, and sometimes v3 of the same API simultaneously. Doing this without a dedicated API gateway quickly becomes a nightmare of custom middleware, routing rules, and documentation drift.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
