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

Congratulations! 🎊 You have completed this course and learned how to build a complete reactive web application including the backend and the frontend.

# The journey so far

You started with an overview of the full reactive stack and the application that you were going to build. Afterward, you followed along with an extended tutorial on building each part of the application. Initially, you built the reactive and non-reactive versions to compare their performance. Then, you moved on to building the Angular frontend that had the blocking service as well as the reactive service to provide a comparison. Finally, you concluded with a comparison of the reactive approach versus the traditional stack in terms of user experience, performance, and ease of development.

## Takeaways
- You were able to analyze the pros and cons of reactive (and asynchronous) patterns applied to the web.

- You were able to understand the basic concepts of Project Reactor and WebFlux: Fluxes, Monos, and backpressure.

- You implemented a reactive database access layer with Spring Data and MongoDB.

- You wrote a reactive API at the controller level with Reactor's Fluxes.

- You learned the basics about Server-Sent Events and put them into practice.

- You built a basic Angular frontend that consumes the reactive APIs.

- You established an understanding of the EventSource API and how it can be linked to an RxJS' Observable.

- You became skilled at running performance tests against blocking and non-blocking APIs under simulated slow network conditions.

- You compared blocking APIs and reactive APIs in terms of performance, user experience, and ease of development.

Let’s take a moment to reflect on your journey throughout this course.

Reactive Web

Full Reactive Stack Backend

Connecting Angular With the WebFlux Backend

Conclusion

Appendix

Reflection on the Journey

The journey so far