👁 announcement - icon
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
eBook – Guide Spring Cloud – NPI EA (cat=Spring Cloud)
eBook – Mockito – NPI EA (tag = Mockito)
👁 announcement - icon
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
eBook – Java Concurrency – NPI EA (cat=Java Concurrency)
👁 announcement - icon
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
eBook – Reactive – NPI EA (cat=Reactive)
👁 announcement - icon
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
eBook – Java Streams – NPI EA (cat=Java Streams)
👁 announcement - icon
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
eBook – Jackson – NPI EA (cat=Jackson)
eBook – HTTP Client – NPI EA (cat=Http Client-Side)
eBook – Maven – NPI EA (cat = Maven)
eBook – Persistence – NPI EA (cat=Persistence)
eBook – RwS – NPI EA (cat=Spring MVC)
Course – LS – NPI EA (cat=Jackson)
👁 announcement - icon
Get started with Spring and Spring Boot, through the Learn Spring course:
>> LEARN SPRINGCourse – RWSB – NPI EA (cat=REST)
👁 announcement - icon
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Course – LSS – NPI EA (cat=Spring Security)
👁 announcement - icon
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Course – LSD – NPI EA (tag=Spring Data JPA)
👁 announcement - icon
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Partner – Moderne – NPI EA (cat=Spring Boot)
👁 announcement - icon
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Course – LJB – NPI EA (cat = Core Java)
1. Overview
In our Intro to Project Reactor, we learned about Mono<T>, which is a publisher of an instance of type T.
In this quick tutorial, we’ll demonstrate both a blocking and non-blocking way to extract T from the Mono: block and subscribe.
2. Blocking Way
In general, Mono completes successfully by emitting an element at some point in time.
Let’s start with an example publisher Mono<String>:
Mono<String> blockingHelloWorld() {
return Mono.just("Hello world!");
}
String result = blockingHelloWorld().block();
assertEquals("Hello world!", result);Here, we’re blocking the execution as long as the publisher doesn’t emit the value. However, it can take any amount of time to finish.
To get more control, we’ll set an explicit duration:
String result = blockingHelloWorld().block(Duration.of(1000, ChronoUnit.MILLIS));
assertEquals(expected, result);If the publisher doesn’t emit a value within the set duration, a RuntimeException is thrown.
Additionally, Mono could be empty and the block() method above would return null. In that case, we could make use of blockOptional:
Optional<String> result = Mono.<String>empty().blockOptional();
assertEquals(Optional.empty(), result);In general, blocking contradicts the principles of reactive programming. It’s highly discouraged to block the execution in reactive applications.
So now let’s see how to get the value in a non-blocking way.
3. Non-Blocking Way
First of all, we should subscribe in a non-blocking way using the subscribe() method. We’ll also specify the consumer of the final value:
blockingHelloWorld()
.subscribe(result -> assertEquals(expected, result));Here, even if it takes some time to produce the value, the execution immediately continues without blocking on the subscribe() call.
In some cases, we’ll want to consume the value in intermediate steps. Therefore, we can use an operator to add behavior:
blockingHelloWorld()
.doOnNext(result -> assertEquals(expected, result))
.subscribe();4. Conclusion
In this brief article, we explored two ways of consuming a value produced by Mono<String>.
The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.
