In the past years I have been working on multiple projects where the so-called Data Transfer Object (short DTO) pattern has been heavily used. This is a pattern that has even been a core pattern in the JEE world. This pattern certainly has its justification for the right cases. But in many cases I have seen it applied inappropriately. This blog posting by Adam Bien, a JEE advocate, is outlining the case where it should be considered useful. However when applied, this pattern comes at the cost of additional code to maintain and some extra CPU cycles for doing the mapping.

The agents have no explicit consul configuration. So in case consul is running with default settings, nomad will connect using the defaults (https://www.nomadproject.io/docs/configuration/consul).

The following describes selected improvements of the Java JVM. See the Java 18 release notes.

With JEP-400, now UTF-8 is the default charset of the standard Java APIs.

In JDK 17 and earlier, the default charset is determined when the Java runtime starts. On macOS, it is UTF-8 except in the POSIX C locale. On other operating systems, it depends upon the user’s locale and the default encoding, e.g., on Windows, it is a codepage-based charset such as windows-1252 or windows-31j.

The following describes selected improvements of the Java language. See the Java 18 release notes. See Java Language Updates for Java SE 18.

Java 18 is introducing the following language enhancements as developer preview.

With a snippet region defined we can include a fragment of compileable and tested code.

With a snippet tag we can just inline code. There is no need to escape or use HTML.