The switch case expressions in Java go back pretty much to the beginnings of the programming language. It was basically a compromise in language design to make it easier for C++ developers to switch to Java. Relics like break and fall-through were not very intuitive and caused a lot of errors. In addition, the case statement was very limited regarding the notation of the values. Fortunately, this all changes with Java 12. The syntax has been slightly modified to allow specifying one expression and multiple values. In this way, case differences can be formulated much more elegantly.
Developers take advantage of the JVM argument -XX:+UseGCLogFileRotation to rotate GC log files. However, this approach has few challenges. In this article, JAX London speaker Ram Lakshmanan has some recommendations on how to deal with those issues.
Anyone who has ever set up a domain with microservices already knows: APIs for service-to-service communication are of crucial importance. Since each team has its own style and implements interfaces differently, the number of various approaches tends to explode sooner or later. Defining a guideline with rules and examples right at the beginning of the project helps to guarantee consistent APIs which are as self-explanatory as possible.
Microservices lead to new challenges, making it necessary to find new technological approaches. Microservice frameworks are of course part of the solution, but they are certainly not the most important. Which technologies play a crucial role here?
The developer world is fast and constantly changing. Find out what Quentin Adam has to say about keeping up with the new Java cycle and why the language’s future has never looked brighter.
When do reactive streams in Enterprise Java make sense? In this article, Arne Limburg explores the fundamentals of reactive streams in Enterprise Java and goes over how it can be useful for developers.