Pro Spring MVC with Webflux: how important is it to learn WebFlux?

[Junilu Lacar]

Hello authors!

Can you tell us more about the book's focus specifically on Webflux? How important is Webflux going to be in the Spring ecosystem and application architecture? How and where does Webflux fit into the overall Spring MVC architecture? Just want to get some idea of the important points around these questions that you discuss in your book.

Thanks!

[iuliana cosmina]

Most microservices nowadays are reactive. Spring Boot is one of the most used tools to write and deploy microservices quickly. Spring Webflux provides a lot of components to build reactive microservices quite easily.
When everything you interractive around you, you have to adapt, right? So, Sring Webflux is very important for building reactive microservices with Spring.

As for Spring Webflux and MVC, they integrate together nicely, because in the same application  you might have bits that hsould n ott be reactive. For example, when logging into an application using a login form, there's no point having a reactive controller to handle the user logging in, since giving him access to something is dependent on him bbeing logged in.  But after logging in, you might have a page depicting some data that gets updated in real time, and that data should be handled by a reactive component - either a reactive controller of handler function.

In the book there are quite a few examplle that combine classic Sprring MVC components with reactive Webflux ones.

I hope this answers your question.
Cheers!

[T H Lim]

iuliana cosmina wrote:Most microservices nowadays are reactive. Spring Boot is one of the most used tools to write and deploy microservices quickly. Spring Webflux provides a lot of components to build reactive microservices quite easily.
...
As for Spring Webflux and MVC, they integrate together nicely, because in the same application  you might have bits that hsould n ott be reactive. For example, when logging into an application using a login form, there's no point having a reactive controller to handle the user logging in, since giving him access to something is dependent on him bbeing logged in.  But after logging in, you might have a page depicting some data that gets updated in real time, and that data should be handled by a reactive component - either a reactive controller of handler function.
...

I hope this answers your question.
Cheers!

I am confused why a login controller should not be a reactive controller. My understanding for reactive is to reuse the same thread for something else while waiting for the database or auth server response. Yes, the user cannot proceed without authorization, but while waiting for the request to be authenticated, the server thread can be used to serve other requests. There are other processes similar to the login process where some steps must be performed before it can proceed further. Does that mean these processes should not use a reactive controller? Thanks