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.

Turning old as a developer is hard. It is hard to stay relevant, hard to keep up with the competition of newcomers and hard to know all of those new frameworks, tools, languages and practices.
However, the truth is that we oldies have a big advantage over the younglings. We are slow! Slow is good! So whatever you do, don’t put your programming on the shelf just because someone half as old writes code with twice the speed.
I really believe that we need to take a step back, embrace the skill of being slow and change the developer culture to understand that the best way to go fast in the long run often is to be “controlled slow” in the short run.

In this highly interactive talk I will elaborate on the traditional “software developer life cycle” (developer -> team lead -> project leader -> manager) and try to show how we can make those grey hair your biggest asset, just by slowing down.

Java SE 17 was released in September 2022 as the next long-term supported

version from Oracle. Therefore, it is expected that many of us will quite soon migrate

from Java 11 to 17.

In this lecture, we will go through the new APIs available in Java 17, compared to the

ones available in Java 11. We will focus on changes that are most relevant for

developers. Other new features like security enhancements, garbage collector

updates or performance improvements are not in scope of this lecture.

We will cover the following new APIs:

• Text Blocks – make our multiline strings more readable
• Pattern Matching – create variables with instance-of checks
• Records - create immutable data classes with ease
• Sealed Classes - finer control of our class extendibility
• Stream toList Method – reduce boilerplate for the most common collector
• NullPointerExceptions – helpful messages that ease debugging
• Switch Expressions – using arrow functions and getting rid of breaks
• Pattern Matching for Switch – unfortunately only in preview mode

At the end of this lecture, we should be familiar with the latest Java APIs and be

ready to start using Java 17 on your next project assignment.

Every six months, we have a new Java release. And to be a practical Java engineer, you should know about what is new in your language. This session will sweep the dust over Java SE 16 hidden gems, including new cool language features, compiler changes, library additions, and critical bug fixes. What we’re going to look at here are all reasonably tremendous & they’re handy in your day-to-day work. Let’s take a features tour powered by code about Java 16 and future Java 17 LTS.

‍