<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vertx on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/vertx/</link>
    <description>Recent content in Vertx on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/vertx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Reactive Libraries in 2026: Project Reactor vs RxJava vs Vert.x — Which One Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-10-java-reactive-libraries-project-reactor-rxjava-vertx-guide/</link>
      <pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-10-java-reactive-libraries-project-reactor-rxjava-vertx-guide/</guid>
      <description>&lt;h2 id=&#34;blocking-threads-are-the-silent-killer-of-java-services&#34;&gt;Blocking Threads Are the Silent Killer of Java Services&lt;/h2&gt;&#xA;&lt;p&gt;A single slow database call can pin a 200-thread Tomcat pool, and when one endpoint degrades, the whole application grinds to a halt. Reactive programming flips the model: instead of one thread per request, a handful of event-loop threads process thousands of concurrent requests using non-blocking I/O. Three frameworks dominate this space on the JVM — &lt;strong&gt;Project Reactor&lt;/strong&gt;, &lt;strong&gt;RxJava&lt;/strong&gt;, and &lt;strong&gt;Eclipse Vert.x&lt;/strong&gt; — and choosing the wrong one can lock you into an architecture you will fight for years.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
