The current state of these stream application is about a Reactive Streams as much as possible.
It is better to expose management of the generated apps via Spring WebFlux and its Netty foundation.
Premise: the current http-source is fully reactive and expects to be exposed over Netty.
Looks like the generated app comes with Tomcat, for which Spring MVC does only a simulation for Reactive Stream over Servlet container.
The current state of these stream application is about a Reactive Streams as much as possible. It is better to expose management of the generated apps via Spring WebFlux and its Netty foundation.
Premise: the current
http-source
is fully reactive and expects to be exposed over Netty. Looks like the generated app comes with Tomcat, for which Spring MVC does only a simulation for Reactive Stream over Servlet container.