Java Records: How to use a Java Record in a Spring Boot Application

In this tutorial, you will learn about Java Records and how to use them in a Spring Boot Application. Records give you a way to create immutable data classes, cut down on verbosity, and improve readability. There are 3 really good use cases for using the Java Record type in Spring Boot and you will learn about 2 of them today.
👋🏻 Connect with me:
Website: www.danvega.dev
Twitter: / therealdanvega
Github: github.com/danvega
LinkedIn: / danvega
Newsletter: www.danvega.dev/newsletter
SUBSCRIBE TO MY CHANNEL: bit.ly/2re4GH0 ❤️

[@uncopino]

yes please, i’d love a tutorial about records with springdata

[@khajalieubarrie5088]

Records can be used for defining DTO's but understanding how DTO's are manged in the persistence context will help in understanding how records can be used with springdata. This video is a thorough explanation on that:
czcams.com/video/SyP258VgzSs/video.html

[@aminesafi7261]

Great content, nice explanation, keep going 💪🏻

[@kingstonmocktail7744]

Would be great to see how we can use records in Spring Data

[@DanVega]

I will work on a tutorial for that. If you don't want to wait check out Spring Data JDBC, you won't be able to use them with JPA.

[@uncopino]

@@DanVega i looked into spring data jdbc, found a tutorial and the guy said “it’s preferred to work with immutable classes”. is that the reason why it works with records?

[@nomad5297]

Spring Dat JPA requires no args constructor and setters. record does not provide it

[@letme4u]

nice presentation with clear understanding. Please provide next with Spring data

[@DanVega]

Will do, thanks for watching!

[@kumarabhishek7877]

++ Spring Boot Latest update, Dan you are awesome keep sharing the best of you.

[@Pwjdjskw]

I was using Kotlin mainly because I love how simple it is to make data classes but now I am just finding out a very similar thing is in Java now?? Let’s go!

[@Matlaps123]

Fantastic. Please do the JPA!

[@DanVega]

You can’t use records with JPA

[@felixnjunge78]

Hello Dan, while using records can I annotate, Json annotations, @Column annotations as I would one a normal class

[@geoffreymakawa3554]

Hey Dan, what plugin are you using to be able to get those intellisense auto completion suggestions ?

[@felixnjunge78]

I think that is Github copilot

[@jopadjr]

9th.. Thanks.

[@graflaszlo]

Just keep it in this way :-)

[@MartenJurgenson]

Hi! What is the Intellij plugin that helps you to complete code? It is suggesting in grey.

[@DanVega]

GitHub Copilot

[@Adam-lx4et]

Looks good in theory but when record has a lot of properties then I can imagine its not great to read and write when using the constructor, in those cases a standard class with a lombok builder would be a more readable approach.

[@layla.visuals3923]

@configuration properties is throwing error with java records - Update your configuration so that classname is defined via @ConfigurationPropertiesScan or @EnableConfigurationProperties., even ehen using the above ending up with other error

[@jassebozic2504]

👍

[@domincwild]

What about classes which have a lot of properties? This is nice for small data classes, but what if it has something like 20 different properties that must be set?

[@DanVega]

It will work for those as well. I have IntelliJ automatically put each argument on a new line for readability.

[@domincwild]

@@DanVega That's good. Although I'm mainly thinking about usage. So it would be readable inside the class, but when its used somewhere in the code, a 20 arg constructor is pretty unweildy. Say I wanted most of these values to have sensible defaults, but still be immutable and gain the advantage of a record type.
Something usually solved with the builder pattern, but wondering if this could be applied in some way to simplify that.

[@DanVega]

There isn't much you can do in that case. You can't use the compact constructor to delegate to another constructor so setting defaults that way isn't possible. If you need something like that just use a regular class and use records where possible.

[@jythejavaguy]

@@domincwild One approach is to write custom constructors that delegate to the canonical constructor with default values. And if you need something more like a builder, there are third party libraries that provide builder functionality for Java Records, but you can write your own "wither" if you want:
For example:
record Point3D(int x, int y, int z) {
Point3D() {
this(0,0,0);
}
public Point3D withX(int newX) {
return new Point3D(newX, y, z);
}
}
var point = new Point3D();
point = point.withX(5);

[@glowiever]

I still feel scared that somehow there's a jpa bug waiting around somewhere when I use record...

[@travellogger5080]

Hm... Hm... Case class?