<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Adam Warski on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/adam-warski/</link><description>Recent content in Adam Warski on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 04 Apr 2025 12:27:42 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/adam-warski/index.xml" rel="self" type="application/rss+xml"/><item><title>From Reactive Streams to Virtual Threads</title><link>https://javapro-en.svenruppert.com/from-reactive-streams-to-virtual-threads/</link><pubDate>Fri, 04 Apr 2025 12:27:42 +0000</pubDate><guid>https://javapro-en.svenruppert.com/from-reactive-streams-to-virtual-threads/</guid><description>&lt;p&gt;Virtual Threads deliver a fast, cheap (in terms of memory &amp;amp; switching speed) threading solution for the JVM. They promise the return of a direct-style, synchronous programming model. But is that enough to challenge the status quo regarding data streaming? Can we have the best of both worlds: the simplicity that Virtual Threads promise and the resilience and safety of Reactive Streams? Let&amp;rsquo;s find out!&lt;/p&gt;
&lt;p&gt;First, a little bit of history. Virtual Threads were released with Java 21 in September 2023, after 6 years of development. Some final limitations of that implementation will be fully lifted with the release of Java 24 in March 2025. &lt;/p&gt;</description></item></channel></rss>