Writing code that others can understand without hassle is an art. An important issue in this challenge is proper documentation of the code - not overly extensive, but also not the often encountered zero-documentation-way.

JUnit offers great possibilities to write good tests with ease. Expressing the intention of tests and test classes with the @DisplayName annotation and structuring them with @Nested is a good practice, causes only minor effort and helps reducing the pain of adapting tests when the code under test has changed.

Having migrated to RESTEasy Reactive sporadic SocketExceptions occurred in one of our AWS Lambdas several minutes after the actual Lambda execution. This article describes one possible solution for this problem by disabling the connection pool for the used REST client with the help of custom HttpClientOptions but of course with the price of a lower overall performance.

Until Quarkus 2.8 RESTEasy Classic was the default JAX-RS implementation when using REST in a Quarkus project. Then they switched over to RESTEasy Reactive, which is the reactive version but also contains the classic blocking flavor. This post summarizes my experiences with the migration to RESTEasy Reactive.