<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shared-Memory on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/shared-memory/</link>
    <description>Recent content in Shared-Memory on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 28 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/shared-memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; Inter-Process Communication Libraries: Eclipse Iceoryx vs Boost.Interprocess vs nng</title>
      <link>https://www.pistack.xyz/posts/2026-06-28-cpp-ipc-libraries-eclipse-iceoryx-boost-interprocess-nng/</link>
      <pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-28-cpp-ipc-libraries-eclipse-iceoryx-boost-interprocess-nng/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Inter-process communication (IPC) is the backbone of modular system architecture. When processes need to exchange data — whether on the same machine through shared memory or across a network via message passing — the choice of IPC library fundamentally shapes your system&amp;rsquo;s latency, throughput, and operational complexity. The C++ ecosystem offers three distinct IPC paradigms: zero-copy shared memory (Eclipse Iceoryx), traditional shared memory primitives (Boost.Interprocess), and brokerless network messaging (nng).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
