Spring MVC (async) vs Spring WebFlux

Question

I\'m trying to understand Spring WebFlux. The things I\'ve found so far are reactive at the core, no Servlet API, no thread per request, HTTP 2, server pushes, application/strea

Answer 1

Servlet API is blocking I/O which requires 1 thread per HTTP request. Spring MVC async relies on Servlet APIs which only provides async behavior between container threads and request processing threads but not end to end.

Spring WebFlux on the other hand achieves concurrency by a fixed number of threads by using HTTP sockets and pushing chunks of data at a time through the sockets. This mechanism is called event loop, an idea made popular by Node.js. Such an approach is scalable and resilient. Spring 5's spring-webflux uses the event loop approach to provide async behavior.

More can be read from

• Servlet vs. Reactive
• Spring Boot performance battle
• Comparing WebFlux with Spring Web MVC