<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Non-Blocking on wid's blog</title><link>https://wid-blog.github.io/en/tags/non-blocking/</link><description>Recent content in Non-Blocking on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 25 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/non-blocking/index.xml" rel="self" type="application/rss+xml"/><item><title>Spring WebFlux Fundamentals — Non-blocking I/O and the Reactive Stack</title><link>https://wid-blog.github.io/en/posts/tech/language/spring-webflux-reactive-stack/</link><pubDate>Mon, 25 Mar 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/language/spring-webflux-reactive-stack/</guid><description>Spring MVC assigns one thread per request. When I/O waits pile up, threads sit idle. WebFlux replaces this with an event loop-based non-blocking model. A summary of the structural differences from MVC, the Reactor pattern, and when to choose which.</description></item></channel></rss>