<story><title>Achieving 5M persistent connections with Project Loom virtual threads</title><url>https://github.com/ebarlas/project-loom-c5m</url></story><parent_chain></parent_chain><comment><author>cheradenine_uk</author><text>I think a lot of people are missing the point.&lt;p&gt;Go look at the sourcecode. Look at how simple it is - anyone who has created a thread with java knows what&amp;#x27;s happening. With only minor tweaks, this means your pre-existing code can take advantage of this with, basically, no effort. And it retains all the debuggability of traditional java thread (I.e: a stack trace that makes sense!)&lt;p&gt;If you&amp;#x27;ve spent any time at all dealing with the horrors of c# async&amp;#x2F;await (Why am I here? Oh, no idea) and it&amp;#x27;s doubling of your APIs to support function colouring - or, you&amp;#x27;ve fought with the complexities of reactive solutions in the Java space -- often, frankly, in the name of &amp;quot;scalability&amp;quot; that will never be practically required -- this is a big deal.&lt;p&gt;You no longer have to worry about any of that.</text></comment>
<story><title>Achieving 5M persistent connections with Project Loom virtual threads</title><url>https://github.com/ebarlas/project-loom-c5m</url></story><parent_chain></parent_chain><comment><author>pron</author><text>For more information about virtual threads see &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;openjdk.java.net&amp;#x2F;jeps&amp;#x2F;425&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;openjdk.java.net&amp;#x2F;jeps&amp;#x2F;425&lt;/a&gt; (planned to preview in JDK 19, out this September).&lt;p&gt;What&amp;#x27;s remarkable about this experiment is that it uses simple 26-year-old (Java 1.0) networking APIs.</text></comment>