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

We want to connect to the backend from a client application that is deployed *at a different origin because it uses a different port* (at least during development). In web terms, that means the frontend will do a *cross origin request*. Unless we explicitly allow CORS (*Cross-Origin Resource Sharing*) in our configuration, that connection is going to be rejected.

## `CorsWebFilter` bean

To enable CORS with WebFlux globally, one of the options is to inject a `CorsWebFilter` bean in the context with custom configuration of the allowed origins, methods, headers, etc. We'll configure it to allow any method and header from the origin, `localhost:4200`, where our frontend will be deployed.


We want to connect to the backend from a client application that is deployed *at a different origin because it uses a different port* (at least during development). In web terms, that means the frontend will do a *cross origin request*. Unless we explicitly allow CORS (*Cross-Origin Resource Sharing*) in our configuration, that connection is going to be rejected.

# `CorsWebFilter` bean

To enable CORS with WebFlux globally, one of the options is to inject a `CorsWebFilter` bean in the context with custom configuration of the allowed origins, methods, headers, etc. We'll configure it to allow any method and header from the origin, `localhost:4200`, where our frontend will be deployed.


Learn how to enable cross-origin resource sharing in Spring Webflux. Also, learn how the client application's request can activate the reactive functionality in Spring.

Reactive Web

Full Reactive Stack Backend

Connecting Angular With the WebFlux Backend

Conclusion

Appendix

Enabling CORS in Spring WebFlux and Returning a Flux

`CorsWebFilter` bean