<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>In-Process on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/in-process/</link>
    <description>Recent content in In-Process on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/in-process/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Event Bus Libraries: EventBus vs Guava vs MBassador vs Otto — In-Process Pub-Sub Comparison</title>
      <link>https://www.pistack.xyz/posts/2026-06-21-event-bus-libraries-eventbus-guava-mbassador-otto/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-21-event-bus-libraries-eventbus-guava-mbassador-otto/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When building complex server-side applications, managing communication between components without tight coupling is a fundamental challenge. While message brokers like RabbitMQ and NATS handle inter-service communication, &lt;strong&gt;in-process event buses&lt;/strong&gt; solve a different problem: enabling decoupled communication between components within the same application process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
