https://foojayio.github.io/website/today/author/bjorn-vdlaan/Articles written by Bjorn van der Laan on foojay.io - Friends of OpenJDKHugoen-usThu, 09 Dec 2021 14:03:28 +0000https://foojayio.github.io/website/today/build-and-test-non-blocking-web-applications-with-spring-webflux-kotlin-and-coroutines/Thu, 09 Dec 2021 14:03:28 +0000https://foojayio.github.io/website/today/build-and-test-non-blocking-web-applications-with-spring-webflux-kotlin-and-coroutines/<p>When a HTTP request comes in, a &rsquo;normal&rsquo; web application would map the request to a specific thread from the thread pool. This assigned thread stays with the request until a response can be returned to the request socket. Along the way, we might need to fetch data from some web service or database, read or write to a file or do other I/O calls, during which the thread is blocked and has to wait until it gets a response. For applications with high request rates, the thread pool can at some point become exhausted and then no new requests can be handled anymore.</p>