Value object

In computer science, a value object is a small object that represents a simple entity whose equality is not based on identity: i.e. two value objects are equal when they have the same value, not necessarily being the same object.^[1][2]

Examples of value objects are objects representing an amount of money or a date range.

Being small, one can have multiple copies of the same value object that represent the same entity: it is often simpler to create a new object rather than rely on a single instance and use references to it.^[2]

Value objects should be immutable:^[3] this is required for the implicit contract that two value objects created equal, should remain equal. It is also useful for value objects to be immutable, as client code cannot put the value object in an invalid state or introduce buggy behaviour after instantiation.^[4]

Value objects work better if they have native support for copy-by-value semantics, i.e. the expression

valueObject1 = valueObject2

assigns the value of the valueObject1 by creating a copy of the valueObject2, instead of assigning a reference to the second object, as happens in most object oriented languages for assignments among objects.^[5]

Value objects are among the building blocks of DDD.

Value objects in C#

In C# a class is a reference type while a struct (concept derived from the struct in C language) is a value type.^[6] Hence an instance derived from a class definition is an object while an instance derived from a struct definition is said to be a value object (to be precise a struct can be made immutable to represent a value object declaring attributes as readonly^[7]).

The main differences between objects and value objects in C# are that:

• objects are mutable
• value objects are immutable
• objects are referenced and the expression object1 = object2 assigns to object1 a reference to object2
• value objects are copied by value (cloned): hence the expression valueObject1 = valueObject2 makes a copy of the values of the attributes of valueObject2 to those of valueObject1.

The memory management is also different: if a struct is declared as a local variable in C#, its data is kept in the stack with other local variables, while for classes the data is always stored in the heap memory (as variables only receive a pointer to this memory). This memory management can help in terms of performance.^[8]

Value Objects in Java

Unlike C# and C++, Java has no support for custom value types at the language level. Every custom type is a reference type, and therefore has identity and reference semantics,^[9] though extending support for custom value types is being considered.^[10]

Java programmers therefore emulate value objects by creating immutable objects,^[11] because if the state of an object does not change, passing references is semantically equivalent to copying value objects.

A class can be made immutable by declaring all attributes blank final,^[12] and declaring all attributes to be of immutable type (such as String, Integer, or any other type declared in accordance with these rules), not of mutable type such an ArrayList or even a Date. They should also define equals and hashCode to compare values rather than references.

The term "VALJO" (VALue Java Object) has been coined to refer to the stricter set of rules necessary for a correctly defined immutable value object.^[13]

Value Objects in C++

In C++ a value object can be built by overloading the assignment operator and using appropriate constness constraints on the fields (which will be evaluated once by the initializer list of the constructor) and on the methods of the class.

However, if the fields themselves are declared const (rather than use non-const fields while only exposing "getter" accessors), then it won't be possible to fully overwrite such a value object with another ( object1 = object2).

See also

• Data transfer object
• Domain-driven design
• Value semantics

References