When should a domain concept be a value object?
When it is defined entirely by its attributes, has no lifecycle of its own, and can be treated as immutable and replaceable: money, date ranges, addresses, coordinates. Making these value objects removes primitive obsession and puts validation in one place.
Answered in
Entities, Value Objects, Aggregates: DDD's Building Blocks via Their Hardest QuestionsHow do you compare two entities? Two value objects? What does an aggregate protect? DDD's building blocks, explained by the question each one answers.
Read the full analysisOther questions this article answers
More development best practices questions
- What is the primary security vulnerability of storing JWTs in localStorage?
- How do server-side sessions scale horizontally across multiple instances?
- Why is immediate revocation nearly impossible with stateless JWTs?
- What is the recommended modern authentication architecture for SaaS apps?
- What is the N+1 query problem in GraphQL and how is it fixed?
- How does GraphQL Federation allow multiple backend teams to maintain one API?
- Why is caching harder in GraphQL than in traditional REST APIs?
- When should an engineering team prefer REST or gRPC over GraphQL?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.