title: DDD - Two aggregate roots sharing same database table in a single bounded context
body: <p>I have a first aggregate root having a natural Id encapsulating invariants related to a same topic.</p>
  
  <p>Suddently, a new business requirement arises with a new set of invariants on a completely different topic than the first aggregate. It is a great occasion to create a new aggregate root in same bounded context.</p>
  
  <p>However, both aggregate roots have the same natural Id. And both aggregate roots have some identical properties (but not all). Those identical properties can be modified, but I don't want to kick-in a flow of domain events to propagate data changes in those two aggregates (because we cannot modify two aggregates in the same transaction).</p>
  
  <p>An option would be to regroup those aggregate roots. They are in the same bounded context and they have the same natural Id (they "represent" the same thing) so it feels natural. But with that option, the aggregate would become HUGE. Size is not a real problem, but merging really different kinds of invariants bother me.</p>
  
  <p>What about keeping those aggregates separated in the domain, but rely on the same database table to share the data? </p>
  
  <p>Any opinion on that?
  On another alternative?</p>