<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Backend on Raul&#39;s Blog</title>
    <link>https://blog.rulyotano.com/tags/backend/</link>
    <description>Recent content in Backend on Raul&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jun 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.rulyotano.com/tags/backend/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reliable Microservice Communication: Patterns That Keep Distributed Systems Sane</title>
      <link>https://blog.rulyotano.com/articles/reliable-microservices-communication/</link>
      <pubDate>Tue, 30 Jun 2026 09:00:00 +0000</pubDate>
      <guid>https://blog.rulyotano.com/articles/reliable-microservices-communication/</guid>
      <description>&lt;p&gt;Distributed systems fail in ways that monoliths never do. In a single process, if a function call fails you get an exception — simple, local, easy to reason about. Spread that same call across a network boundary and suddenly you&amp;rsquo;re dealing with partial failures, redelivered messages, timeouts that may or may not mean the operation succeeded, and cascading outages that start from something as mundane as a slow database query.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
