Additional Notes
When should you keep a traditional class?
Track: Java
Topic: Modern Java
Focus: Java Records
Java: Java Records
Answer
When the model needs mutable state or richer lifecycle behavior.
A behavior-heavy aggregate is not the same as a simple data carrier. Records are deliberately constrained, so a normal class is often a better fit for complex mutable business objects.
A behavior-heavy aggregate is not the same as a simple data carrier. Records are deliberately constrained, so a normal class is often a better fit for complex mutable business objects.
Topics: Java Java Records Modern Java