All videos
Kotlin + Spring 5.0 Web Flux

Almost nobody likes big changes. This includes management and developers. It is often very hard to convince people to try something new. Even if the old way is pathetic, leads to bugs and does not fit to a problem. If you do not believe in that try to convince any JavaEE/ Spring team to use something else. Even though both platforms are quite dated and do not really enable writing clean code. They are even worse if you try functional programming.

The way I often do is to introduce only small improvements, to the extent that might get accepted by the team and managers. Such a trick is to use Kotlin as Java++ and Spring 5… as just a new version of Spring. After a while, it can appear that the “new Java” is written totally functional, with very little or none mutability. And the new Spring works without annotations and so-called beans. Eventually, we get a code that is more similar to Scala/Akka-HTTP stack… that would not be ever accepted.