mn create-app example.micronaut.micronautguide \
--features=yaml,data-mongodb-reactive,reactor \
--build=maven \
--lang=java \
--test=junit
Access a MongoDB database asynchronously with Micronaut Data MongoDB and Reactive Streams
Learn how to access a MongoDB database asynchronously with Micronaut Data.
Authors: Tim Yates
Micronaut Version: 4.6.3
1. Getting Started
In this guide, we will create a Micronaut application written in Java.
You will use MongoDB for persistence.
2. What you will need
To complete this guide, you will need the following:
-
Some time on your hands
-
A decent text editor or IDE (e.g. IntelliJ IDEA)
-
JDK 17 or greater installed with
JAVA_HOME
configured appropriately -
Docker installed to run MongoDB and to run tests using Testcontainers.
3. Solution
We recommend that you follow the instructions in the next sections and create the application step by step. However, you can go right to the completed example.
-
Download and unzip the source
4. Writing the Application
Create an application using the Micronaut Command Line Interface or with Micronaut Launch.
If you don’t specify the --build argument, Gradle with the Kotlin DSL is used as the build tool. If you don’t specify the --lang argument, Java is used as the language.If you don’t specify the --test argument, JUnit is used for Java and Kotlin, and Spock is used for Groovy.
|
The previous command creates a Micronaut application with the default package example.micronaut
in a directory named micronautguide
.
If you use Micronaut Launch, select Micronaut Application as application type and add yaml
, data-mongodb-reactive
, and reactor
features.
If you have an existing Micronaut application and want to add the functionality described here, you can view the dependency and configuration changes from the specified features, and apply those changes to your application. |
4.1. Dependencies
In this guide, we use the MongoDB Reactive driver.
The data-mongodb-reactive
features adds the following dependencies:
<!-- Add the following to your annotationProcessorPaths element -->
<path>
<groupId>io.micronaut.data</groupId>
<artifactId>micronaut-data-document-processor</artifactId>
</path>
<dependency>
<groupId>io.micronaut.data</groupId>
<artifactId>micronaut-data-mongodb</artifactId>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.mongodb</groupId>
<artifactId>mongodb-driver-reactivestreams</artifactId>
<scope>runtime</scope>
</dependency>
4.2. POJO
Create a Fruit
POJO:
package example.micronaut;
import io.micronaut.core.annotation.NonNull;
import io.micronaut.core.annotation.Nullable;
import io.micronaut.data.annotation.GeneratedValue;
import io.micronaut.data.annotation.Id;
import io.micronaut.data.annotation.MappedEntity;
import jakarta.validation.constraints.NotBlank;
@MappedEntity (1)
public class Fruit {
@Id (2)
@GeneratedValue
private String id;
@NonNull
@NotBlank (3)
private final String name;
@Nullable
private String description;
public Fruit(@NonNull String name, @Nullable String description) {
this.name = name;
this.description = description;
}
public String getId() {
return id;
}
public void setId(String id) {
this.id = id;
}
@NonNull
public String getName() {
return name;
}
@Nullable
public String getDescription() {
return description;
}
public void setDescription(@Nullable String description) {
this.description = description;
}
}
1 | Annotate the class with @MappedEntity to map the class to the table defined in the schema. |
2 | Specifies the ID of an entity |
3 | Use jakarta.validation.constraints Constraints to ensure the data matches your expectations. |
4.3. Repository
Create a repository interface to encapsulate the CRUD actions for Fruit
.
package example.micronaut;
import io.micronaut.core.annotation.NonNull;
import io.micronaut.data.mongodb.annotation.MongoRepository;
import io.micronaut.data.repository.reactive.ReactiveStreamsCrudRepository;
import org.reactivestreams.Publisher;
import java.util.List;
@MongoRepository (1)
public interface FruitRepository extends ReactiveStreamsCrudRepository<Fruit, String> { (2)
@NonNull
Publisher<Fruit> findByNameInList(@NonNull List<String> names); (3)
}
1 | Annotate with @MongoRepository . |
2 | Extend ReactiveStreamsCrudRepository for asynchronous database access. |
3 | Add a finder for finding fruit by a list of names. |
4.4. Service
Create a service FruitService
as an API to interact with the Fruit
repository.
This will allow you to keep business logic out of the controller, and to test the controller later without interacting with a real database.
package example.micronaut;
import io.micronaut.core.annotation.NonNull;
import org.reactivestreams.Publisher;
import java.util.List;
interface FruitService {
Publisher<Fruit> list();
Publisher<Fruit> save(Fruit fruit);
Publisher<Fruit> find(@NonNull String id);
Publisher<Fruit> findByNameInList(List<String> name);
}
And then create a default implementation of this service.
package example.micronaut;
import io.micronaut.core.annotation.NonNull;
import jakarta.inject.Singleton;
import org.reactivestreams.Publisher;
import java.util.List;
@Singleton (1)
class DefaultFruitService implements FruitService {
private final FruitRepository fruitRepository;
public DefaultFruitService(FruitRepository fruitRepository) {
this.fruitRepository = fruitRepository;
}
public Publisher<Fruit> list() {
return fruitRepository.findAll();
}
public Publisher<Fruit> save(Fruit fruit) {
if (fruit.getId() == null) {
return fruitRepository.save(fruit);
} else {
return fruitRepository.update(fruit);
}
}
public Publisher<Fruit> find(@NonNull String id) {
return fruitRepository.findById(id);
}
public Publisher<Fruit> findByNameInList(List<String> name) {
return fruitRepository.findByNameInList(name);
}
}
1 | Use jakarta.inject.Singleton to designate a class as a singleton. |
4.5. Controller
Create FruitController
:
package example.micronaut;
import io.micronaut.core.annotation.NonNull;
import io.micronaut.core.async.annotation.SingleResult;
import io.micronaut.http.HttpStatus;
import io.micronaut.http.annotation.Controller;
import io.micronaut.http.annotation.Get;
import io.micronaut.http.annotation.PathVariable;
import io.micronaut.http.annotation.Post;
import io.micronaut.http.annotation.Put;
import io.micronaut.http.annotation.QueryValue;
import io.micronaut.http.annotation.Status;
import jakarta.validation.Valid;
import jakarta.validation.constraints.NotNull;
import org.reactivestreams.Publisher;
import java.util.List;
@Controller("/fruits") (1)
class FruitController {
private final FruitService fruitService;
FruitController(FruitService fruitService) { (2)
this.fruitService = fruitService;
}
@Get (3)
Publisher<Fruit> list() {
return fruitService.list();
}
@Post (4)
@Status(HttpStatus.CREATED) (5)
@SingleResult
Publisher<Fruit> save(@NonNull @NotNull @Valid Fruit fruit) { (6)
return fruitService.save(fruit);
}
@Put
@SingleResult
Publisher<Fruit> update(@NonNull @NotNull @Valid Fruit fruit) {
return fruitService.save(fruit);
}
@Get("/{id}") (7)
Publisher<Fruit> find(@PathVariable String id) {
return fruitService.find(id);
}
@Get("/q") (8)
Publisher<Fruit> query(@QueryValue @NotNull List<String> names) { (9)
return fruitService.findByNameInList(names);
}
}
1 | The class is defined as a controller with the @Controller annotation mapped to the path /fruits . |
2 | Use constructor injection to inject a bean of type FruitService . |
3 | The @Get annotation maps the list method to an HTTP GET request on /fruits . |
4 | The @Post annotation maps the save method to an HTTP POST request on /fruits . |
5 | You can specify the HTTP status code via the @Status annotation. |
6 | Add @Valid to any method parameter which requires validation. |
7 | The @Get annotation maps the find method to an HTTP GET request on /fruits/{id} . |
8 | The @Get annotation maps the findByNameInList method to an HTTP GET request on /fruits/q . |
9 | Bind a list of Strings to the query parameter names |
4.6. Test Client
Add a Micronaut declarative HTTP Client to src/test
to ease the testing of the application’s API.
package example.micronaut;
import io.micronaut.http.HttpResponse;
import io.micronaut.http.annotation.Get;
import io.micronaut.http.annotation.PathVariable;
import io.micronaut.http.annotation.Post;
import io.micronaut.http.annotation.Put;
import io.micronaut.http.annotation.QueryValue;
import io.micronaut.http.client.annotation.Client;
import jakarta.validation.constraints.NotNull;
import java.util.List;
import java.util.Optional;
@Client("/fruits")
interface FruitClient {
@Get
Iterable<Fruit> list();
@Get("/{id}")
Optional<Fruit> find(@PathVariable String id);
@Get("/q")
Iterable<Fruit> query(@QueryValue @NotNull List<String> names);
@Post
HttpResponse<Fruit> save(Fruit fruit);
@Put
Fruit update(Fruit fruit);
}
Then create a test that verifies the validation of the Fruit
POJO when we create a new entity via POST
:
package example.micronaut;
import io.micronaut.http.HttpRequest;
import io.micronaut.http.HttpStatus;
import io.micronaut.http.client.HttpClient;
import io.micronaut.http.client.annotation.Client;
import io.micronaut.http.client.exceptions.HttpClientResponseException;
import io.micronaut.test.extensions.junit5.annotation.MicronautTest;
import jakarta.inject.Inject;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertThrows;
@MicronautTest(transactional = false) (1)
class FruitValidationControllerTest {
@Inject
@Client("/")
HttpClient httpClient;
@Test
void fruitIsValidated() {
HttpClientResponseException exception = assertThrows(
HttpClientResponseException.class,
() -> httpClient.toBlocking().exchange(HttpRequest.POST("/fruits", new Fruit("", "")))
);
assertEquals(HttpStatus.BAD_REQUEST, exception.getStatus());
}
}
1 | Annotate the class with @MicronautTest so the Micronaut framework will initialize the application context and the embedded server. By default, each @Test method will be wrapped in a transaction that will be rolled back when the test finishes. This behaviour is is changed by setting transaction to false . |
Transaction mode is not supported when the synchronous transaction manager is created using Reactive transaction manager! |
Create a test that checks our controller works against a real MongoDB database:
package example.micronaut;
import io.micronaut.http.HttpResponse;
import io.micronaut.http.HttpStatus;
import io.micronaut.test.extensions.junit5.annotation.MicronautTest;
import jakarta.inject.Inject;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.Test;
import reactor.core.publisher.Flux;
import java.util.Arrays;
import java.util.List;
import java.util.stream.Collectors;
import java.util.stream.Stream;
import java.util.stream.StreamSupport;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertNull;
import static org.junit.jupiter.api.Assertions.assertTrue;
@MicronautTest(transactional = false) (1)
class FruitControllerTest {
@Inject
FruitClient fruitClient;
@Inject
FruitRepository fruitRepository;
@AfterEach (2)
void cleanup() {
Flux.from(fruitRepository.deleteAll()).blockFirst();
}
@Test
void emptyDatabaseContainsNoFruit() {
assertEquals(0, StreamSupport.stream(fruitClient.list().spliterator(), false).count());
}
@Test
void testInteractionWithTheController() {
HttpResponse<Fruit> response = fruitClient.save(new Fruit("banana", null));
assertEquals(HttpStatus.CREATED, response.getStatus());
Fruit banana = response.getBody().get();
Iterable<Fruit> fruits = fruitClient.list();
List<Fruit> fruitList = StreamSupport.stream(fruits.spliterator(), false).toList();
assertEquals(1, fruitList.size());
assertEquals(banana.getName(), fruitList.get(0).getName());
assertNull(fruitList.get(0).getDescription());
response = fruitClient.save(new Fruit("apple", "Keeps the doctor away"));
assertEquals(HttpStatus.CREATED, response.getStatus());
fruits = fruitClient.list();
assertTrue(StreamSupport.stream(fruits.spliterator(), false)
.anyMatch(f -> "Keeps the doctor away".equals(f.getDescription())));
banana.setDescription("Yellow and curved");
fruitClient.update(banana);
fruits = fruitClient.list();
assertEquals(
Stream.of("Keeps the doctor away", "Yellow and curved").collect(Collectors.toSet()),
StreamSupport.stream(fruits.spliterator(), false)
.map(Fruit::getDescription)
.collect(Collectors.toSet())
);
}
@Test
void testSearchWorksAsExpected() {
fruitClient.save(new Fruit("apple", "Keeps the doctor away"));
fruitClient.save(new Fruit("pineapple", "Delicious"));
fruitClient.save(new Fruit("lemon", "Lemonentary my dear Dr Watson"));
Iterable<Fruit> fruit = fruitClient.query(Arrays.asList("apple", "pineapple"));
assertTrue(StreamSupport.stream(fruit.spliterator(), false)
.allMatch(f -> f.getName().equals("apple") || f.getName().equals("pineapple")));
}
}
1 | Annotate the class with @MicronautTest so the Micronaut framework will initialize the application context and the embedded server. By default, each @Test method will be wrapped in a transaction that will be rolled back when the test finishes. This behaviour is is changed by setting transaction to false . |
2 | Clean up the database after each test method execution. |
And finally, create a test which uses a replacement FruitService
to test the controller without touching the database:
package example.micronaut;
import io.micronaut.context.annotation.Property;
import io.micronaut.context.annotation.Replaces;
import io.micronaut.context.annotation.Requires;
import io.micronaut.core.type.Argument;
import io.micronaut.http.HttpHeaders;
import io.micronaut.http.HttpRequest;
import io.micronaut.http.HttpResponse;
import io.micronaut.http.HttpStatus;
import io.micronaut.http.MediaType;
import io.micronaut.http.MutableHttpRequest;
import io.micronaut.http.client.HttpClient;
import io.micronaut.http.client.annotation.Client;
import io.micronaut.test.extensions.junit5.annotation.MicronautTest;
import jakarta.inject.Inject;
import jakarta.inject.Singleton;
import jakarta.validation.constraints.NotNull;
import org.junit.jupiter.api.Test;
import org.reactivestreams.Publisher;
import reactor.core.publisher.Flux;
import reactor.core.publisher.Mono;
import java.util.List;
import java.util.stream.Collectors;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertTrue;
@MicronautTest(transactional = false) (1)
@Property(name = "spec.name", value = "controller-isolation")
class ControllerIsolationTest {
@Inject
@Client("/")
HttpClient httpClient;
@Test
void checkSerialization() {
MutableHttpRequest<Object> get = HttpRequest.GET("/fruits");
HttpResponse<List<Fruit>> response = httpClient.toBlocking().exchange(get, Argument.listOf(Fruit.class));
assertEquals(HttpStatus.OK, response.getStatus());
assertEquals(MediaType.APPLICATION_JSON, response.getHeaders().get(HttpHeaders.CONTENT_TYPE));
assertTrue(response.getBody().isPresent());
String all = response.getBody().get().stream().map(f -> f.getName() + ":" + f.getDescription()).collect(Collectors.joining(","));
assertEquals("apple:red,banana:yellow", all);
}
@Singleton
@Replaces(DefaultFruitService.class)
@Requires(property = "spec.name", value = "controller-isolation")
static class MockService implements FruitService {
@Override
public Publisher<Fruit> list() {
return Flux.just(
new Fruit("apple", "red"),
new Fruit("banana", "yellow")
);
}
@Override
public Publisher<Fruit> save(Fruit fruit) {
return Mono.just(fruit);
}
@Override
public Publisher<Fruit> find(@NotNull String id) {
return Mono.empty();
}
@Override
public Publisher<Fruit> findByNameInList(List<String> name) {
return Flux.empty();
}
}
}
1 | Annotate the class with @MicronautTest so the Micronaut framework will initialize the application context and the embedded server. By default, each @Test method will be wrapped in a transaction that will be rolled back when the test finishes. This behaviour is is changed by setting transaction to false . |
5. Test Resources
When the application is started locally — either under test or by running the application — resolution of the property mongodb.uri
is detected and the Test Resources service will start a local MongoDB docker container, and inject the properties required to use this as the datasource.
When running under production, you should replace this property with the location of your production MongoDB instance via an environment variable.
MONGODB_URI=mongodb://username:password@production-server:27017/databaseName
For more information, see the MongoDB section of the Test Resources documentation.
6. Testing the Application
To run the tests:
./mvnw test
7. Running the Application
To run the application, use the ./mvnw mn:run
command, which starts the application on port 8080.
curl -d '{"name":"Pear"}' \
-H "Content-Type: application/json" \
-X POST http://localhost:8080/fruits
curl -i localhost:8080/fruits
HTTP/1.1 200 OK
date: Wed, 15 Sep 2021 12:40:15 GMT
Content-Type: application/json
content-length: 110
connection: keep-alive
[{"name":"Pear"}]
8. Next steps
Explore more features with Micronaut Guides.
Read more about the integration between the Micronaut Data and MongoDB.
9. Help with the Micronaut Framework
The Micronaut Foundation sponsored the creation of this Guide. A variety of consulting and support services are available.
10. License
All guides are released with an Apache license 2.0 license for the code and a Creative Commons Attribution 4.0 license for the writing and media (images…). |