<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compatibility on Nalar</title>
    <link>https://nalar.dev/tags/compatibility/</link>
    <description>Recent content in Compatibility on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/compatibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Evolving APIs Without Breaking Clients</title>
      <link>https://nalar.dev/evolving-apis-without-breaking-clients/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/evolving-apis-without-breaking-clients/</guid>
      <description>&lt;p&gt;An API is not only an HTTP path or function signature. It is a contract about syntax, semantics, timing, errors, ordering, defaults, and lifecycle.&lt;/p&gt;&#xA;&lt;p&gt;Breaking changes often happen because a server remains syntactically compatible while changing one of those less-visible assumptions.&lt;/p&gt;&#xA;&lt;p&gt;Safe API evolution starts by identifying what clients can reasonably depend on and designing changes that allow old and new versions to coexist.&lt;/p&gt;&#xA;&lt;h2 id=&#34;compatibility-has-multiple-dimensions&#34;&gt;Compatibility has multiple dimensions&lt;/h2&gt;&#xA;&lt;p&gt;A change can preserve JSON shape and still break clients.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
