Gain insights into building Reactive Web Applications with Spring Boot 2 and Spring WebFlux, from database integration to front-end. Explore Reactive vs MVC, performance, and deployment with Docker.   


Full Reactive Stack with Spring Boot 2 and Spring WebFlux.png

tarball.tar.gz

initialzr

spring-mongo-only

Lesson-playing-with-reactive-endpoints

angular-app-with spring-mongo

angular-app-with spring-mongo-copy

spring-mongo-only-copy

initialzr-copy

This course is your guide to using Spring Boot 2 and Spring WebFlux to create Reactive Web Applications. 

You will learn how to build a full-reactive system from the database (MongoDB reactive) to the front-end (Angular), using a Reactive programming strategy leveraged by Spring WebFlux, with the simplicity offered by Spring Boot 2. 

Beyond that though, you will be able to compare the Spring WebFlux with the standard MVC approach as well, covering the main aspects such as simplicity, performance, user experience, and more.

The last part of the course ties it all up by teaching you to run the application using Docker compose. By the end of this course, you will have a great new skill for your resume and you’ll be able to build your own projects using the full Reactive stack.

Full Reactive Stack: Spring Boot 2 & Spring WebFlux

To better show the comparison between the blocking and reactive approaches, let’s create a separate controller with different request paths, and connect them to a standard `CrudRepository`. This code is pretty straightforward and well-known to developers familiar with Spring Web MVC.

# Blocking controller

Let's look at the controller's code. 

> Note, that here, we also apply the same delay (`DELAY_PER_ITEM_MS` on `line 13`) as in the reactive approach. However, this time, the delay is a big one (it adds up), since the query is returning results at once too.


Learn how to create a blocking controller and a blocking repository and learn how they differ from their reactive counterparts.

Reactive Web

Full Reactive Stack Backend

Connecting Angular With the WebFlux Backend

Conclusion

Appendix

Blocking Controller and Repository