create-value-object

Primitive obsession occurs when you use raw strings and numbers instead of domain concepts. Create immutable value objects that wrap primitives with validation and business logic, ensuring type safety and enforcing domain rules at the boundary—for example, an EmailField that validates format or a PriceField that prevents negative values.

Build reusable value objects with built-in validation through static factory methods that throw domain-specific exceptions on invalid input. This centralizes validation logic, eliminating scattered checks and ensuring consistency wherever those values appear in your codebase.

Define immutable final classes with private constructors and static factory methods (fromString, fromInt, etc.). Include comparison methods, accessors, and optional business logic. This pattern creates type-safe, reusable components that prevent accidental mutation and encode domain constraints.

Use value objects to encapsulate concepts like prices, emails, quantities, and IDs that carry meaning beyond their primitive type. Value objects are particularly valuable in shared contexts and bounded contexts where multiple aggregates reference the same domain concept.

Yes. Place shared, reusable value objects under Shared/Entities/VO for use across bounded contexts. Place bounded-context-specific value objects under their respective BC/Entities/VO folders. This structure supports both reuse and context isolation.

Yes. Value objects can include optional business logic beyond validation—for example, a PriceField can implement currency conversion methods. The immutable pattern and static factories keep the implementation clean while encoding domain operations.