DTO Pattern vs Record in Java: A Comparison

· 2 min read
javadtorecordarchitecture

Introduction

Data transfer between layers is a core concern in Java applications. Two common approaches are traditional DTO classes and Java Records.

Both can represent data contracts, but each has different trade-offs.

DTO Pattern

A DTO (Data Transfer Object) is typically a class with fields, constructors, getters/setters, and optional utility methods.

Example

public class UserDto {
  private String id;
  private String name;
  private String email;

  public UserDto(String id, String name, String email) {
    this.id = id;
    this.name = name;
    this.email = email;
  }

  public String getId() { return id; }
  public String getName() { return name; }
  public String getEmail() { return email; }

  public void setName(String name) { this.name = name; }
}

Benefits

  • Flexible for custom behavior and validation.
  • Good compatibility with older Java versions and frameworks.
  • Fine-grained control over serialization and mutability.

Drawbacks

  • More boilerplate code.
  • Tends to become verbose as models grow.

Java Records

Records (finalized in Java 16) offer a compact way to represent immutable data carriers.

Example

public record UserRecord(String id, String name, String email) {}

Records automatically provide constructor, accessors, equals, hashCode, and toString.

Benefits

  • Very concise syntax.
  • Immutable by default.
  • Strong readability for simple data contracts.
  • Naturally thread-safe due to immutability.

Drawbacks

  • Less suitable for mutable objects.
  • Limited when you need richer behavior in the same type.
  • Not ideal for cases requiring highly customized object lifecycle.

When to Use Each

Use DTOs when:

  • You need mutable structures.
  • You need custom validation or transformation logic in the object.
  • Legacy compatibility is a requirement.

Use Records when:

  • You need immutable data carriers.
  • You want minimal boilerplate.
  • You prioritize simplicity and clear contracts.

Conclusion

DTOs and Records both solve data transfer, but with different priorities. DTOs maximize flexibility; Records maximize simplicity and immutability. Choose based on the constraints of your architecture, framework, and domain model.

All articles