Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add notes on future deprecation of the RestTemplate

Browse Source 
Issue: SPR-16993
This commit is contained in:
Rossen Stoyanchev
2018-07-27 08:32:59 -04:00
parent fcbf06f050
commit 91d17cf628
5 changed files with 45 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
src/docs/asciidoc/integration.adoc
View File

@@ -950,14 +950,18 @@ plugging in third-party or custom solutions here.
The Spring Framework provides two choices for making calls to REST endpoints:
* <<rest-resttemplate>> -- the original Spring REST client with an API similar to other
template classes in Spring such as `JdbcTemplate`, `JmsTemplate` and others.
`RestTemplate` has a synchronous API and relies on blocking I/O which is okay for
client scenarios with low concurrency.
* <<web-reactive.adoc#webflux-client,WebClient>> -- reactive client with a functional,
fluent API from the `spring-webflux` module. It relies on non-blocking I/O which allows it
to support high concurrency more efficiently (i.e. using a small number of threads) than the
`RestTemplate`. `WebClient` is a natural fit for streaming scenarios.
* <<rest-resttemplate>> -- the original Spring REST client with a synchronous, template
method API.
* <<web-reactive.adoc#webflux-client,WebClient>> -- non-blocking, reactive alternative
that supports both sync and async, as well as streaming scenarios.
[NOTE]
====
As of 5.0, the non-blocking, reactive `WebClient` offers a modern alternative to the
`RestTemplate` with efficient support for both sync and async, as well as streaming
scenarios. The `RestTemplate` will be deprecated in a future version and will not have
major new features gong forward.
====
[[rest-resttemplate]]