Databases
StackOverflow2013
Postsdbo
PODDD Bounded Context "integration"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODDD Bounded Context "integration"
    primarykey
    data
    text
    <p>We're trying to figure out the separated bounded context integration for a scenario.</p> <p>Say one context is the <em>Document Core</em> Bounded Context <strong>(BC)</strong> and has a <em>Document</em> Entity, with an <em>Author</em>. Using the <em>IdentityAccessContext</em> <strong>BC</strong> as in the <a href="http://rads.stackoverflow.com/amzn/click/0321834577" rel="nofollow">Implementing DDD book</a> which separates <em>Users, Groups, and Roles</em> into their own context makes sense.</p> <p>The problem that is occurring is when considering fetching a list of say 100+ Documents. </p> <p>Say the Document Core <strong>BC</strong> has it's own Entity to mark the Author of a Document.</p> <pre><code>public class Author { long Id; // Same as UserId long Document; } </code></pre> <p>And then the Identity <strong>BC</strong> has a User with relevant info.</p> <pre><code>public class User { long Id; string FullName; } </code></pre> <p>When fetching a List of <em>Documents</em>, how is the information from the <em>IdentityAccess</em> <strong>BC</strong> supposed to be retrieved into/with the <em>Document Author</em> for displaying (Full Name for example)?</p> <p>There seem to be a couple alternatives:</p> <ol> <li>Perhaps a <strong>Anti-corruption Layer</strong> which fetches data from both tables?</li> <li>Duplicate the user's full name across the two <strong>BC's</strong>?</li> </ol> <p>Neither feel quite right, since #1 requires joining data (at some level) from 2 BC's, while #2 requires potentially updating several BC's when changing the user's name.</p> <p>What can be done about this? (<em>Using C#, MVC, NHibernate if that matters</em>) Clearly fetching a list of objects and later fetching e.g. the Author's name and additional data later isn't realistic.</p> <p><em>When looking at the <strong>BC</strong> integration, however, given the 3 options mentioned in the book RPC, Domain Events, and RESTful service integration, at least the latter 2 don't make sense in this case where the application is MVC, and it directly uses the 2 BC's as class libraries and they both use the same database. Updating Users information can be done directly from MVC through the Identity <strong>BC's</strong> Application Services.</em> The database and BC can be changed as/if needed.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USlko
    1. USlko
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODDD Bounded Context "integration"
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODDD Bounded Context "integration"
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODDD Bounded Context "integration"
      1. USJefClaes
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload