Skip to content

Commit 1c90d48

Browse files
committed
Rename Motivation to Overview and restore sub-sections
1 parent d16a710 commit 1c90d48

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

src/docs/asciidoc/web/webflux.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ for example, Spring MVC controllers with the reactive `WebClient`.
1818

1919

2020
[[webflux-new-framework]]
21-
== Motivation
21+
== Overview
2222

2323
Why was Spring WebFlux created?
2424

@@ -41,7 +41,7 @@ WebFlux to offer functional web endpoints alongside annotated controllers.
4141

4242

4343
[[webflux-why-reactive]]
44-
== Define "`Reactive`"
44+
=== Define "`Reactive`"
4545

4646
We touched on "`non-blocking`" and "`functional`" but what does reactive mean?
4747

@@ -74,7 +74,7 @@ If a publisher cannot slow down, it has to decide whether to buffer, drop, or fa
7474

7575

7676
[[webflux-reactive-api]]
77-
== Reactive API
77+
=== Reactive API
7878

7979
Reactive Streams plays an important role for interoperability. It is of interest to libraries
8080
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
103103

104104

105105
[[webflux-programming-models]]
106-
== Programming Models
106+
=== Programming Models
107107

108108
The `spring-web` module contains the reactive foundation that underlies Spring WebFlux,
109109
including HTTP abstractions, Reactive Streams <<webflux-httphandler,adapters>> for supported
@@ -125,7 +125,7 @@ annotations and being called back.
125125

126126

127127
[[webflux-framework-choice]]
128-
== Applicability
128+
=== Applicability
129129

130130
Spring MVC or WebFlux?
131131

@@ -181,7 +181,7 @@ unsure what benefits to look for, start by learning about how non-blocking I/O w
181181

182182

183183
[[webflux-server-choice]]
184-
== Servers
184+
=== Servers
185185

186186
Spring WebFlux is supported on Tomcat, Jetty, Servlet 3.1+ containers, as well as on
187187
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
209209

210210

211211
[[webflux-performance]]
212-
== Performance versus Scale
212+
=== Performance
213213

214214
Performance has many characteristics and meanings. Reactive and non-blocking generally
215215
do not make applications run faster. They can, in some cases, (for example, if using the
@@ -226,7 +226,7 @@ dramatic.
226226

227227

228228
[[webflux-concurrency-model]]
229-
== Concurrency Model
229+
=== Concurrency Model
230230

231231
Both Spring MVC and Spring WebFlux support annotated controllers, but there is a key
232232
difference in the concurrency model and the default assumptions for blocking and threads.

0 commit comments

Comments
 (0)