I like to write code that works. It should perform its job correctly, efficiently and resiliently. It should work under heavy load and even if some errors occur along the way. In order to fulfill all these requirements, I preferably chose one of Java's reactive frameworks for coding. There is a range of them available: Java Reactive Streams, RxJava, Project Reactor and even one called Mutiny. Those Java frameworks can be a lot of fun to use once you get the hang of it. But in my experience that "getting the hang" reactive coding can be quite a challenge. Written mostly in a stream based way, it looks and executes differently than classic imperative code. The learning curve is steep. However, it can be fun. And to proof that, in this live session I am going to write two snippets of code that basically perform the same job. One of them will be written imperatively, the other one will be reactive. I'm sure I'll like the latter one better. What about you?