Uploaded April 2026 | Updated September 2026, 2 weeks ago
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
JEP-395 in Java 16 brought us records to store and model immutable data, allowing developers to replace POJO's in many cases.
In this lightning talk we'll cover the benefits of records, when to migrate towards them and when to retain POJO's. Ensuring your collections remain immutable is also covered, as well as how Lombok could still fit in.
We'll also learn about the various ways to migrate your old code, or prepare them for a later migration easing the amount of work while gaining the maximum amount of benefits from records.
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
JEP-395 in Java 16 brought us records to store and model immutable data, allowing developers to replace POJO's in many cases.
In this lightning talk we'll cover the benefits of records, when to migrate towards them and when to retain POJO's. Ensuring your collections remain immutable is also covered, as well as how Lombok could still fit in.
We'll also learn about the various ways to migrate your old code, or prepare them for a later migration easing the amount of work while gaining the maximum amount of benefits from records.
