domain driven design - Entity/value object selection -
In the domain driven design, it is common knowledge that an object with identification is a unit. For example, any person's identity will have many forms (names, etc.).
But value objects are not identical to those objects, a common value is the object address, although there is no identity of the address. But on the database layer, we can be a composite key, does this concept work in DDD? This will make the address recognizable by combining the road names, postcodes and door numbers (excluding information such as city and city). Money will be another value object.
The difference in an object with a single identifiable field and value objects is not actually related to the institution. For example, "I" (replace with my name) can wear shoes, but "I" is not a shoe, shirt etc.
What is the right way to think about things? Apart from this, with this mentality / attitude, I can apply this value / reference type selection to C #. Can I go with the DDD approach though?
Thanks
I think you have differentiating between institutions and value types Concepts are correct because they are explained within the domain driven design (although I am far away from the expert in this matter - perhaps it is better to say that you match my understanding of these concepts) Advice against use as a metric when I Objects in C # is also referred to as the reference or value.
The main difference between the value and the reference type is that the price type is copied when they are passing through a method, that means they are more likely to sit on the heap instead of the heap And may be more expensive to pass; As the shape becomes a factor for the idea. Recommendation is that under a composition size of 16 bytes (under comment) and a broad address structure (home number, house name, street area, city, country etc.) will be easily broken. share Since changing the address one should not change the address of another person, so the address as a straight will apply such kind of separation. When all the examples of a person in the application are same person). But there are performance and memory considerations. Perhaps the temporary classes will be in good condition for these values?
Briefly: What is the difference between the unit and value in DDD around the object. In the code you intend to do with it.
Comments
Post a Comment