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

# Angular application

To showcase the reactive capabilities, you’ll create a client web application that receives quotes from the book _Don Quixote_. 



## Server-Sent Events channel

Instead of just asking for the quotes using a standard blocking call, you’ll open a [Server-Sent Events channel](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events). If you know about _WebSockets_, you can see this as a similar technology in which the communication is unidirectional (server to client). 

The backend application will send these events (quotes) once there is a subscriber (our client application). This part is supported by WebFlux returning a `Flux<Quote>` object (don’t worry about these terms; we'll cover them later on). On the Angular app's end, you’ll model the connection using an `EventSource` object, mapped to an RxJS’s `Observable<Queue>`.

The Angular component subscribes to the `Observable`, adds the new element to an array, and re-renders the UI.

> While we build the full reactive stack, we'll create a classic blocking approach too. We’ll use it to compare both strategies from the implementation and runtime perspectives.

We’ll dive into the implementation details in the rest of the chapters of this course.


Get familiar with the client web application you will be building. Also, learn how it will communicate with the backend application.

Reactive Web

Full Reactive Stack Backend

Connecting Angular With the WebFlux Backend

Conclusion

Appendix

The Client Web Application

Angular application

Server-Sent Events channel