This is not the expected behavior for any well written service/application. So far so good, but Wait!! Aren’t we missing something? What happens if the blog id we send in the URL does not exist in our map? Will the second mono fetch the blog rating, if the first mono results empty? Will second repository call execute? Let’s see… Empty Mono When we pass blog id = 20, which obviously does not exist in the map, we get an empty response from the service. We were able to combine two mono’s into one and manipulate their response. We can see that the response includes the blog name and rating for that blog. Now, let’s run the service and try to hit the endpoint. Ideally, if our static map contains blog Id we should be able to see the blog detail and its rating. We combine the result obtained from the 2 repository calls using the Mono.zipWith() function. We inject a repository instance to our controller class, and then invoke the repository methods. For the sake of simplicity we will use a static Map as our backend data source.
User has to provide a blog id in the request to get the details and blog rating. This gets you the blog details and its ratings. In the snippet’s above we have defined a simple `BlogController.java` class.
Java merge method map code#
Let us go through the following code snippets: What could go wrong if we do not consider the basics? Scenario How we combine multiple mono’s together?Ģ. It provides the mono and flux API types to work on data sequences 0.1 and 1.n respectively.ġ. Spring web flux uses project reactor at its core for providing the support of reactive streams. The main purpose of reactive streams is to let the subscriber control how fast or slow a publisher produces data. Reactive streams defines the interaction between the asynchronous components with back pressure. This is where reactive streams comes into picture. In a non-blocking environment, it becomes important to control the rate of events so that a fast producer does not overwhelm its destination. We have to provide ways to handle back pressure. One very important thing to consider with non-blocking reactive applications is back pressure. The example of mouse clicks/hovering on UI is quite straight forward. What exactly does it mean to be reactive? The answer is the ability to react to a change almost immediately, like rendering of UI components on mouse click/hover actions. Spring’s support for Reactive micro-service is based on the MONO and FLUX API’s at its core.
Spring boot has provided the support for the same. We focus a lot on non-blocking and asynchronous communication in a reactive micro-service architecture. Hi all, as the title Reactive Java: Combining Mono(s) suggests, here we are going to use spring boot web flux to combine multiple Mono(s) into a single operation using the zipWith() method.
0 kommentar(er)
