Please enable JavaScript.
Coggle requires JavaScript to display documents.
spring webflux, reactive programming - Coggle Diagram
spring webflux
why it was created
for the need for non-blocking web stack
how is non-blocking implemented by libraries?
to handle concurrency with small number of threads
to scale with fewer hardware resources
servlet non-blocking API differs from rest of Servlet APIs
as
those are synchronous
Filter
Servlet
those are blocking
getParameter
getPart
to have common API to serve as foundation across any non-blocking runtime
what are java web non-blocking runtime?
to use functional programming
possible in java due to lambda expression
runs on servers
spring web was for servlet api
Netty
Undertow
Servlet containers
reactive library
spring uses Reactor
fully non-blocking
supports
reactive streams
reactive programming