design patterns - Use of ValueObjects -


i developing entity framework (database first , code first). of time, using entities in domain models, mapped dedicated tables. in ddd, there concept of valueobjects, should have no identity , should immutable. based on experience ddd, how use valueobjects ? concept emerges creating model (for instance, when deals read-only data, parameters...) or there strategic behaviour expected or deductible stating object should designed valueobject (or not), or should immutable (or not) ?

there couple of examples of value objects on so, check question.

value objects equality established not checking if have same id, comparing values itself.

one more thing consider ef not supporting value objects (nhibernate does).


Comments

Popular posts from this blog

php - failed to open stream: HTTP request failed! HTTP/1.0 400 Bad Request -

java - How to filter a backspace keyboard input -

java - Show Soft Keyboard when EditText Appears -