<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Two flavors of DDD</title>
	<atom:link href="http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/feed/" rel="self" type="application/rss+xml" />
	<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/</link>
	<description></description>
	<lastBuildDate>Sat, 28 Jan 2012 14:35:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Sławek Sobótka</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-2346</link>
		<dc:creator><![CDATA[Sławek Sobótka]]></dc:creator>
		<pubDate>Tue, 01 Nov 2011 12:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-2346</guid>
		<description><![CDATA[Great post. It&#039;s good that we are trying to name new patterns in DDD and describe their forces and consequences.

One remark: first approach (Aggregate Graph) is not &quot;more OO&quot;. Actually it&#039;s not OO at all:P
In this approach We are using classes to model data structures, but this doest not mean that using classes automatically imply OO. Traversing &quot;web&quot; of object volatiles two fundamental OO principles:  abstraction and encapsulation/hermetisation.

So second approach that decouples objects, and encapsulates (origin of the data in this case) is more OO:)

@bjdavidson - actually it can be considered as a feature. I&#039;m interested in the data that ware actual at the order confirmation moment. If user changes them later - shipment still goes to the &quot;old&quot; address. Of course if this does not make in particular domain it should be modeled as &quot;Aggregate Graph&quot; or just as ID of the customer if customer is in different Bounded Context (CRM module for example).]]></description>
		<content:encoded><![CDATA[<p>Great post. It&#8217;s good that we are trying to name new patterns in DDD and describe their forces and consequences.</p>
<p>One remark: first approach (Aggregate Graph) is not &#8220;more OO&#8221;. Actually it&#8217;s not OO at all:P<br />
In this approach We are using classes to model data structures, but this doest not mean that using classes automatically imply OO. Traversing &#8220;web&#8221; of object volatiles two fundamental OO principles:  abstraction and encapsulation/hermetisation.</p>
<p>So second approach that decouples objects, and encapsulates (origin of the data in this case) is more OO:)</p>
<p>@bjdavidson &#8211; actually it can be considered as a feature. I&#8217;m interested in the data that ware actual at the order confirmation moment. If user changes them later &#8211; shipment still goes to the &#8220;old&#8221; address. Of course if this does not make in particular domain it should be modeled as &#8220;Aggregate Graph&#8221; or just as ID of the customer if customer is in different Bounded Context (CRM module for example).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bjdavidson</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-1664</link>
		<dc:creator><![CDATA[bjdavidson]]></dc:creator>
		<pubDate>Sun, 04 Jul 2010 14:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-1664</guid>
		<description><![CDATA[What happens if you change the customer name. Do you update the aggregates with the customer snapshot attached? If so isnt this expensive at this point?]]></description>
		<content:encoded><![CDATA[<p>What happens if you change the customer name. Do you update the aggregates with the customer snapshot attached? If so isnt this expensive at this point?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin B. Olesen</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-1371</link>
		<dc:creator><![CDATA[Martin B. Olesen]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 12:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-1371</guid>
		<description><![CDATA[Useful reflections! My own experiences using DDD pretty much mirror yours, but nice to have it put into words.]]></description>
		<content:encoded><![CDATA[<p>Useful reflections! My own experiences using DDD pretty much mirror yours, but nice to have it put into words.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Alsing</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-1370</link>
		<dc:creator><![CDATA[Roger Alsing]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 09:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-1370</guid>
		<description><![CDATA[Snapshots are generally value object and value objects are stored inline in the same table as the owner object.

That is; the product snapshot would be stored together with the order detail data in the same table.

So they are neither projections or separate tables.]]></description>
		<content:encoded><![CDATA[<p>Snapshots are generally value object and value objects are stored inline in the same table as the owner object.</p>
<p>That is; the product snapshot would be stored together with the order detail data in the same table.</p>
<p>So they are neither projections or separate tables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Webster</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-1369</link>
		<dc:creator><![CDATA[James Webster]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 06:55:27 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-1369</guid>
		<description><![CDATA[Interesting... are the CustomerSnapshot and ProductSnapshot objects just projections of a small set of columns from the database&#039;s Customer and Product tables, or are there actual tables that hold this data?]]></description>
		<content:encoded><![CDATA[<p>Interesting&#8230; are the CustomerSnapshot and ProductSnapshot objects just projections of a small set of columns from the database&#8217;s Customer and Product tables, or are there actual tables that hold this data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frans Bouma</title>
		<link>http://rogeralsing.com/2009/11/08/two-flavors-of-ddd/#comment-1368</link>
		<dc:creator><![CDATA[Frans Bouma]]></dc:creator>
		<pubDate>Mon, 09 Nov 2009 09:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=673#comment-1368</guid>
		<description><![CDATA[Insightful as always. :)]]></description>
		<content:encoded><![CDATA[<p>Insightful as always. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

