In the last decade, Spring WebMVC (model-view-controller) has become one of the most popular Java web frameworks. However, since its adoption in 2004, requirements for web applications have significantly changed. Today's web applications face higher user expectations and greater demands than ever before. On the same time, the number of concurrent users is constantly growing.
With the introduction of Spring WebFlux, the reactive model has been brought to the Spring ecosystem as a promising alternative to meet the requirements of modern web applications. However, using Spring WebFlux is two-fold. While it yields a higher through-put and a better resource utilization than Spring WebMVC, there are many pitfalls to consider. A careless utilization may even result in a worse performance.
In one of our projects, we are using Spring WebFlux for over a year now. In this session, we talk about advantages of Spring WebFlux over Spring WebMVC, put a strong focus on common pitfalls and discuss scenarios where it may be more beneficial to stay with Spring WebMVC.
