Comparing WebFlux and Spring MVC with JMeter, Kotlin, and Spock — A concerts registration WebApps example

1. Introduction

Many times, we need to backup certain claims we make in software development. More often than not, we need to show it very clearly to stakeholders, business, and management, the value of our claims. Many times we see a true value in changing some technology and we see long term benefits in doing so. Whether the improvements we see are performance related, code readability, maintainability, modularity, what actually matters to business are other parameters. These can be anything like, fast delivery, feature enabling, image, user experience, profits and business growth. In this way, if we need to make an argument on why we should make a step towards a new technology, we need to be able to justify that. Many times this is not an easy task. We have to clearly identify the business goals and make it clear that our suggestions will make remarkable improvements.

For some time I’ve seen talks about reactive programming and my focus has always been WebFlux. RxJava is on the horizon but that will be subject for another article.

In this article I assume a few things about the readers. Experience and knowledge about MVC and reactive architectures are very important. Therefore the basics are very…