<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Concurrency on Victor Laurance - Software Engineer</title><link>https://laurance.dev/en/tags/concurrency/</link><description>Recent content in Concurrency on Victor Laurance - Software Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://laurance.dev/en/tags/concurrency/index.xml" rel="self" type="application/rss+xml"/><item><title>Virtual Threads and Concurrency in Java 25 with Spring Boot 4</title><link>https://laurance.dev/en/blog/virtual-threads/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://laurance.dev/en/blog/virtual-threads/</guid><description>&lt;p>Every Java backend that needs to handle high concurrent traffic eventually runs into the same fundamental constraint: operating system threads are expensive. Each one reserves stack memory, and the operating system cannot sustain more than a few thousand of them without degrading. For years, the industry&amp;rsquo;s answer was migrating to reactive stacks: WebFlux, Reactor, and callbacks—trading simple imperative code for a programming model that is markedly harder to read and debug. Virtual Threads arrived specifically to eliminate that bottleneck without forcing developers to pay that complexity tax, and Java 25 has finally matured this capability far beyond its initial release in 2023.&lt;/p></description></item></channel></rss>