Spring Reactive - Lesson 3 - Handling errors when calling endpoints

In this new series, we learn to build reactive apps with Spring and Spring Boot. We discuss:

- Basic contracts: Publisher, Mono, Flux, Subscriber, etc.
- Implementing reactive REST endpoints
- Connecting reactively to a relational database using Spring Data
- Connecting reactively to non-relational database using Spring Data
- Many more

Code on GitHub:

[annapureddyravi]

Thank you so much I was searching this kind of lesson

[aniket]

Hi Laurentiu, here we are adding Flux<Product> as the return type. But can we seperate Flux with business object Product? I assume service layer should be un-aware about reactive implementation. So it can return just List<Product> which helps to segregate responsibility and same service will be used if we totally remove reactive approach and go for HTTP non-reactive one and also unit testing of service would become simpler