title: Domain Driven Design - update of value objects
body: <p>I'm quite new to DDD and I'm still reading about it. While reading I had some doubt about aggregates sharing some data with other aggregates.
  As an example, assume that I'm developing an online store, I would model an Account aggregate and an Order aggregate. Now, assume that some of the data of the Account aggregate is really needed by the Order aggregate to accomplish all business cases. Following DDD strictly, I should model the Order aggregate to have a value object holing the identity of the Account aggregate and ask for the needed Account data all the time. Should I still model it as a value object holding the identity and always ask for the needed data or can I create the value object so that it holds the needed data all the time?</p>
  <p><a href="https://i.stack.imgur.com/icZ7I.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/icZ7I.png" alt="enter image description here" /></a></p>
  <p>This way the data is always around, however, this data also need to be in sync with the real Account aggregate data.</p>
  <p>Thank you</p>