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

You can build a reactive web API using Servlet 3.0 and returning Java's Callable objects.

You can build a reactive web API using Servlet 3.0 and returning Java’s Callable objects.

Your frontend application is reactive if it calls the backend API with *promise* objects and updates the DOM asynchronously.

Your frontend application is reactive if it calls the backend API with promise objects and updates the DOM asynchronously.

Spring provides reactive support on top of the Spring Web (or MVC) module.

Spring provides reactive support on top of the Spring Web (or MVC) module.

WebFlux is based on which of the following:

WebFlux is based on which of the following:

The API consumer retrieves all the data in less time.

Users with slow Internet connections get a better experience.

The server can handle more connections efficiently.

Which of the following are benefits of Spring Webflux?

Which of the following are benefits of Spring Webflux?

Reactive frameworks based on the Reactive Streams specification implement patterns like:

Reactive frameworks based on the Reactive Streams specification implement patterns like:

The data producer slows down serving data when there are many subscribers.

The subscriber can signal the publisher to slow down when needed.

The subscriber implements a buffer to make sure it can cope with all the data produced.

The backpressure concept could be defined as:

The backpressure concept could be defined as:

Are unidirectional channels for the server to push data to the frontend

Implement the same functionality as WebSockets: a bidirectional channel between the frontend and the backend

Reactive Web

Full Reactive Stack Backend

Connecting Angular With the WebFlux Backend

Conclusion

Appendix

Quiz: Reactive Web