Once the feature of web reactive programming was added in the Spring framework, most of us started comparing and wondering which one was better. There is nothing compatible, or even incompatible, between these two ways of programming. To end users, it's the result; only beneath the line, things will be different. How much do we, as developers, want to enhance the user experience and how much asynchronous support do we want to add will decide whether to use the traditional way of coding to deal with web request or to use new paradigm of programming called reactive programming. It's impossible to leave an existing application behind and start supporting only the new way. Spring web MVC on the Servlet 3.1 stack is still completely supported and, along with it, Spring web reactive is supported by Tomcat, Jetty, Undertow, and Netty-like Servlet containers.
The Spring Reactive framework, though based on the Reactor project, also supports the RxJava...