@@ -18,7 +18,7 @@ for example, Spring MVC controllers with the reactive `WebClient`.
18
18
19
19
20
20
[[webflux-new-framework]]
21
- == Motivation
21
+ == Overview
22
22
23
23
Why was Spring WebFlux created?
24
24
@@ -41,7 +41,7 @@ WebFlux to offer functional web endpoints alongside annotated controllers.
41
41
42
42
43
43
[[webflux-why-reactive]]
44
- == Define "`Reactive`"
44
+ === Define "`Reactive`"
45
45
46
46
We touched on "`non-blocking`" and "`functional`" but what does reactive mean?
47
47
@@ -74,7 +74,7 @@ If a publisher cannot slow down, it has to decide whether to buffer, drop, or fa
74
74
75
75
76
76
[[webflux-reactive-api]]
77
- == Reactive API
77
+ === Reactive API
78
78
79
79
Reactive Streams plays an important role for interoperability. It is of interest to libraries
80
80
and infrastructure components but less useful as an application API, because it is too
@@ -103,7 +103,7 @@ of RxJava or another reactive library. See <<webflux-reactive-libraries>> for mo
103
103
104
104
105
105
[[webflux-programming-models]]
106
- == Programming Models
106
+ === Programming Models
107
107
108
108
The `spring-web` module contains the reactive foundation that underlies Spring WebFlux,
109
109
including HTTP abstractions, Reactive Streams <<webflux-httphandler,adapters>> for supported
@@ -125,7 +125,7 @@ annotations and being called back.
125
125
126
126
127
127
[[webflux-framework-choice]]
128
- == Applicability
128
+ === Applicability
129
129
130
130
Spring MVC or WebFlux?
131
131
@@ -181,7 +181,7 @@ unsure what benefits to look for, start by learning about how non-blocking I/O w
181
181
182
182
183
183
[[webflux-server-choice]]
184
- == Servers
184
+ === Servers
185
185
186
186
Spring WebFlux is supported on Tomcat, Jetty, Servlet 3.1+ containers, as well as on
187
187
non-Servlet runtimes such as Netty and Undertow. All servers are adapted to a low-level,
@@ -209,7 +209,7 @@ For Undertow, Spring WebFlux uses Undertow APIs directly without the Servlet API
209
209
210
210
211
211
[[webflux-performance]]
212
- == Performance versus Scale
212
+ === Performance
213
213
214
214
Performance has many characteristics and meanings. Reactive and non-blocking generally
215
215
do not make applications run faster. They can, in some cases, (for example, if using the
@@ -226,7 +226,7 @@ dramatic.
226
226
227
227
228
228
[[webflux-concurrency-model]]
229
- == Concurrency Model
229
+ === Concurrency Model
230
230
231
231
Both Spring MVC and Spring WebFlux support annotated controllers, but there is a key
232
232
difference in the concurrency model and the default assumptions for blocking and threads.
0 commit comments