<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Event-Loop on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/event-loop/</link>
    <description>Recent content in Event-Loop on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/event-loop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; Async Event Loop Frameworks: Seastar vs libuv vs libevent vs uvw</title>
      <link>https://www.pistack.xyz/posts/2026-06-30-cpp-async-event-loop-frameworks-seastar-libuv-libevent-uvw/</link>
      <pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-30-cpp-async-event-loop-frameworks-seastar-libuv-libevent-uvw/</guid>
      <description>&lt;p&gt;Modern C++ applications handling thousands of concurrent connections need efficient async I/O. Choosing the right event loop framework shapes your architecture&amp;rsquo;s scalability, latency profile, and developer experience. This guide compares four leading C++ async event loop frameworks — &lt;strong&gt;Seastar&lt;/strong&gt;, &lt;strong&gt;libuv&lt;/strong&gt;, &lt;strong&gt;libevent&lt;/strong&gt;, and &lt;strong&gt;uvw&lt;/strong&gt; — across design philosophy, performance characteristics, API ergonomics, and production usage.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
