<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Fahd El Mazouni - Blog</title>
  <link>https://fel-mazo.com/en/blog/</link>
  <description>Writing on backend architecture, API design, and the unglamorous decisions that keep systems running.</description>
  <language>en</language>
  <atom:link href="https://fel-mazo.com/en/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>Designing API boundaries that age well</title>
    <link>https://fel-mazo.com/en/blog/designing-api-boundaries-that-age-well/</link>
    <guid>https://fel-mazo.com/en/blog/designing-api-boundaries-that-age-well/</guid>
    <description>Most APIs start clean. The interesting question is what happens eighteen months later, when three teams depend on your endpoint and nobody remembers why that field is nullable.</description>
    <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
  </item>
</channel>
</rss>
