The post discusses the comparison between Spring WebFlux and Spring MVC architectures by implementing two Spring Boot applications with Kotlin and benchmarking their performances using JMeter. The WebFlux application, which follows a reactive non-blocking model, is compared to the traditional blocking MVC model. It highlights the increased capacity and performance benefits of using WebFlux, especially in handling high-load scenarios. Detailed setup instructions for JMeter and Docker configurations are provided, along with test results showing WebFlux's resilience in processing more requests compared to the MVC architecture.
Table of contents
1. Introduction2. Development2.1. Environment setup2.2. Structure2.3. ER Model2.4. Spring MVC vs WebFlux2.4.1 Data Model2.4.2. Making ER work2.4.3. Repository2.4.4. Service2.4.5. Controllers2.4.6 Dtos3. Testing and benchmarking3.1. JMeter in a nutshell3.2. Running our tests3.2.1. MVC Results3.2.2.. WebFlux Results3.2.3. Mixed Results4. Conclusion5. ResourcesSort: