Reactive Support in the Spring Framework: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=Overview= | =Overview= | ||
Spring 5 comes with a new web reactive stack, consisting of a new reactive web framework, [[Spring WebFlux]], and a reactive REST Client [[Spring WebClient|WebClient]]. Reactive programming support is extended to non-blocking data repositories with reactive support for [[Spring_Data_Redis#Reactive_Redis|Redis]], [[Spring_Data_MongoDB#Reactive_MongoDB|MongoDB]], [[Spring_Data_for_Apache_Cassandra#Reactive_Cassandra|Cassandra]] and [[Spring_Data_Couchbase#Reactive_Couchbase|Couchbase]]. Reactive support is built in top of [[Project Reactor]], a Java library for working with reactive types. | Spring 5 comes with a new web reactive stack, consisting of a new reactive web framework, [[Spring WebFlux]], and a reactive REST Client [[Spring WebClient|WebClient]]. Reactive programming support is extended to non-blocking data repositories with reactive support for [[Spring_Data_Redis#Reactive_Redis|Redis]], [[Spring_Data_MongoDB#Reactive_MongoDB|MongoDB]], [[Spring_Data_for_Apache_Cassandra#Reactive_Cassandra|Cassandra]] and [[Spring_Data_Couchbase#Reactive_Couchbase|Couchbase]]. Reactive support is built in top of [[Project Reactor]], a Java library for working with reactive types. Reactive programming aims to provide greater scalability and improved performance due to better use of a smaller number of threads, thanks to non-blocking operations. | ||
Revision as of 04:57, 10 October 2018
Internal
Overview
Spring 5 comes with a new web reactive stack, consisting of a new reactive web framework, Spring WebFlux, and a reactive REST Client WebClient. Reactive programming support is extended to non-blocking data repositories with reactive support for Redis, MongoDB, Cassandra and Couchbase. Reactive support is built in top of Project Reactor, a Java library for working with reactive types. Reactive programming aims to provide greater scalability and improved performance due to better use of a smaller number of threads, thanks to non-blocking operations.