Скачать или смотреть Understanding the Difference Between Spring @ Async and Spring WebFlux

A comprehensive guide to transitioning from `@ Async` in Spring to the reactive programming model with WebFlux for improved performance and efficiency.
---
This video is based on the question https://stackoverflow.com/q/66281270/ asked by the user 'EngineerTop' ( https://stackoverflow.com/u/15189625/ ) and on the answer https://stackoverflow.com/a/66292592/ provided by the user 'Michael McFadyen' ( https://stackoverflow.com/u/3047038/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Spring @ Async vs Spring WebFlux

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Difference Between Spring @ Async and Spring WebFlux

In the world of Spring Framework, reactive programming has become a significant focus, especially with the introduction of Spring WebFlux. As developers seek to improve application performance and manage asynchronous tasks effectively, they often encounter decisions between using the traditional @ Async annotation or the newer Spring WebFlux model. This guide will address a common dilemma when converting methods from @ Async to a reactive approach with WebFlux.

The Problem

Imagine you have a method decorated with the @ Async annotation, which allows it to execute asynchronously. Here's a simple version of that method:

[[See Video to Reveal this Text or Code Snippet]]

In your controller, this method is called in a typical REST fashion:

[[See Video to Reveal this Text or Code Snippet]]

Here, startProcess(id) is annotated to make an API call using WebFlux, aiming to ensure that the response (HttpStatus.OK) is sent to the caller immediately, regardless of what happens afterward. The challenge comes when you want to remove the @ Async annotation and adopt a fully reactive pattern using WebFlux.

The Solution

Transitioning to a WebFlux approach involves leveraging the power of non-blocking I/O and reactive streams. Instead of using the @ Async annotation, you can subscribe to your "async" task independently to initiate it in the background. Below, we'll outline the updated code and explain the changes step-by-step.

Updated notifyCallback Method

Here’s how you can modify the notifyCallback method to utilize WebFlux effectively:

[[See Video to Reveal this Text or Code Snippet]]

In this updated version, startProcess(id).subscribe() allows the method to kick off the process asynchronously without blocking the main thread.

Reactive Controller Implementation

In the controller, you will also want to return a Mono<Void> to indicate that it's a reactive endpoint, even if you are ultimately returning an empty response:

[[See Video to Reveal this Text or Code Snippet]]

Demonstrating the Functionality

To better illustrate this behavior, you can create an endpoint that simulates a delay and then performs an action, such as logging a message after waiting:

[[See Video to Reveal this Text or Code Snippet]]

When you access this endpoint, it will immediately return a 200 OK response and perform the logging action after 10 seconds without blocking the caller.

Conclusion

By shifting from the @ Async annotation to using WebFlux, you gain powerful capabilities for building highly responsive, non-blocking applications. The asynchronous execution handled by subscribing to a Mono frees up resources and avoids the overhead associated with thread management in traditional asynchronous processing.

This approach allows you to manage asynchronous tasks seamlessly while maintaining the benefits of Spring's reactive programming model. As you continue your journey with Spring WebFlux, remember that it can provide numerous advantages, especially for applications that require high scalability and efficient resource management.

Empower yourself with the knowledge of Spring WebFlux, and take your applications to the next level!