Spring MVC (async) vs Spring WebFlux

64
votes

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/stream+json.

But what is the difference between asynchronous calls in Spring MVC? I mean in Spring MVC when you return Future, DefferedResult and etc you get logic in the request handler (controller method) executed in a separate thread, so you can benefit from saving thread pool resources for dispatching requests as well.

So could you please highlight differences related to that? Why WebFlux is better here?

Thank you for your time very much!

2
javaspringspring-mvcspring-webflux
Reactive programming is push driven and uses a single dispatcher thread (which is highly efficient) whereas the old model is still limited to the number of threads in your thread pool. – M. Deinum
@M. Deinum But in this case I'm limited with load one thread can handle. Why not to use several of them, not just one having multicore system? – Dmitry Senkovich
It is an event dispatcher thread it is an entirely different model. It only dispatches events (very quickly) whereas the other model is still blocking. – M. Deinum
@M. Deinum ok, that is very interesting, I'm sure I should take a look at it, thank you! – Dmitry Senkovich
@M. Deinum, please share request lifecycle – gstackoverflow

2 Answers

50
votes

The Servlet async model introduces an async boundary between the container threads (1 Servlet request/thread model) and the processing of the request in your application. Processing can happen on a different thread or wait. In the end, you have to dispatch back to a container thread and read/write in a blocking way (InputStream and OutputStream are inherently blocking APIs).

With that model, you need many threads to achieve concurrency (because many of those can be blocked waiting for I/O). This costs resources and it can be a tradeoff, depending on your use case.

With non-blocking code, you only need a few threads to process a lot of requests concurrently. This is a different concurrency model; like any model, there are benefits and tradeoffs coming with it.

For more information about that comparison, this Servlet vs. Reactive stacks talk should be of interest.

8
votes

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