<?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/"
		>
<channel>
	<title>Comments on: Domain Model Pattern</title>
	<atom:link href="http://www.udidahan.com/2007/04/21/domain-model-pattern/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Thu, 11 Mar 2010 11:59:32 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JB</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-36533</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Thu, 06 Aug 2009 13:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-36533</guid>
		<description>Yes, Udi, that would most definitely address my issue. Unfortunately it&#039;s not something that&#039;s easily realized since it would involve pretty big management decisions ;)

Maybe the time isn&#039;t right for investments in a Mainframe-To-MSSQL integration. But one can always dream...

/JB</description>
		<content:encoded><![CDATA[<p>Yes, Udi, that would most definitely address my issue. Unfortunately it&#8217;s not something that&#8217;s easily realized since it would involve pretty big management decisions <img src='http://www.udidahan.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Maybe the time isn&#8217;t right for investments in a Mainframe-To-MSSQL integration. But one can always dream&#8230;</p>
<p>/JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: udidahan</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-36526</link>
		<dc:creator>udidahan</dc:creator>
		<pubDate>Wed, 05 Aug 2009 16:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-36526</guid>
		<description>JB,

What I suggest my clients do in cases like yours is to have an additional DB where the work is done against, and have a separate process which synchronizes that against the mainframe.

Would that address your issues?</description>
		<content:encoded><![CDATA[<p>JB,</p>
<p>What I suggest my clients do in cases like yours is to have an additional DB where the work is done against, and have a separate process which synchronizes that against the mainframe.</p>
<p>Would that address your issues?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-36521</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Tue, 04 Aug 2009 16:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-36521</guid>
		<description>Hi Udi,

Thanks for an interesting article. You mention that domain entities should be persisted using ORM. In my organization, most underlying data comes from the legacy mainframe systems and it&#039;s just not well-designed enough to be used with ORM. Is DDD thus not for us? Is there a &quot;next best&quot; practice or are we stuck with the anemic anti-pattern?</description>
		<content:encoded><![CDATA[<p>Hi Udi,</p>
<p>Thanks for an interesting article. You mention that domain entities should be persisted using ORM. In my organization, most underlying data comes from the legacy mainframe systems and it&#8217;s just not well-designed enough to be used with ORM. Is DDD thus not for us? Is there a &#8220;next best&#8221; practice or are we stuck with the anemic anti-pattern?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Entity Services Rollup</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-2136</link>
		<dc:creator>&#187; Entity Services Rollup</dc:creator>
		<pubDate>Fri, 08 Jun 2007 07:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-2136</guid>
		<description>[...] An SOA Service may be implemented using Entity Services, or not. If so, those Entity Services are not allowed to be accessed outside that SOA Service&#8217;s boundary. As such, they are an implementation detail of SOA. In which case we can have very interesting discussions about the relative value of Entity Services over things like the Domain Model Pattern. [...]</description>
		<content:encoded><![CDATA[<p>[...] An SOA Service may be implemented using Entity Services, or not. If so, those Entity Services are not allowed to be accessed outside that SOA Service&#8217;s boundary. As such, they are an implementation detail of SOA. In which case we can have very interesting discussions about the relative value of Entity Services over things like the Domain Model Pattern. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the &#8216;bee log / Domain Model: Less Pattern, More Lifestyle</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1644</link>
		<dc:creator>the &#8216;bee log / Domain Model: Less Pattern, More Lifestyle</dc:creator>
		<pubDate>Tue, 08 May 2007 05:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1644</guid>
		<description>[...] If you can&#8217;t tell I&#8217;m catching up on Udi&#8217;s blog. He&#8217;s got a post up with some commentary about Martin Fowler&#8217;s &#8220;Anemic Domain Model Anti-Pattern&#8221; and&#160;it&#8217;s typically insightful so read it. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you can&#8217;t tell I&#8217;m catching up on Udi&#8217;s blog. He&#8217;s got a post up with some commentary about Martin Fowler&#8217;s &#8220;Anemic Domain Model Anti-Pattern&#8221; and&nbsp;it&#8217;s typically insightful so read it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Database performance optimization</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1524</link>
		<dc:creator>&#187; Database performance optimization</dc:creator>
		<pubDate>Mon, 30 Apr 2007 11:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1524</guid>
		<description>[...] systems. The fact that we use O/R Mapping makes the business logic possible to get right (using the Domain Model Pattern), but adds another dimension to the performance optimization - primarily around limiting the number [...]</description>
		<content:encoded><![CDATA[<p>[...] systems. The fact that we use O/R Mapping makes the business logic possible to get right (using the Domain Model Pattern), but adds another dimension to the performance optimization &#8211; primarily around limiting the number [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wagnerblog.com &#187; Anemic Domain Model Anti-Pattern</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1470</link>
		<dc:creator>wagnerblog.com &#187; Anemic Domain Model Anti-Pattern</dc:creator>
		<pubDate>Sun, 22 Apr 2007 21:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1470</guid>
		<description>[...] has an interesting post about the notion of an Anemic Domain Model Anti-Pattern. He does point out that Datasets frequently go [...]</description>
		<content:encoded><![CDATA[<p>[...] has an interesting post about the notion of an Anemic Domain Model Anti-Pattern. He does point out that Datasets frequently go [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; SQL Injection attacks &#38; O/R mapping</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1455</link>
		<dc:creator>&#187; SQL Injection attacks &#38; O/R mapping</dc:creator>
		<pubDate>Sat, 21 Apr 2007 18:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1455</guid>
		<description>[...] just wanted to mention this added side benefit of moving to the Domain Model pattern - no more SQL injection [...]</description>
		<content:encoded><![CDATA[<p>[...] just wanted to mention this added side benefit of moving to the Domain Model pattern &#8211; no more SQL injection [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; DDD – why bother?</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1454</link>
		<dc:creator>&#187; DDD – why bother?</dc:creator>
		<pubDate>Sat, 21 Apr 2007 18:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1454</guid>
		<description>[...] Driven Design (DDD), alongside its growing popularity, is experiencing some growing pains. The Domain Model pattern, documented in the Patterns of Enterprise Application Architecture book, is at the heart of DDD yet [...]</description>
		<content:encoded><![CDATA[<p>[...] Driven Design (DDD), alongside its growing popularity, is experiencing some growing pains. The Domain Model pattern, documented in the Patterns of Enterprise Application Architecture book, is at the heart of DDD yet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Dataset – O/R mapping rumble at TechEd MVP Dinner</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1452</link>
		<dc:creator>&#187; Dataset – O/R mapping rumble at TechEd MVP Dinner</dc:creator>
		<pubDate>Sat, 21 Apr 2007 18:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1452</guid>
		<description>[...] separately was accepted. Secondly, I proposed that an object model (specifically implementing the Domain Model pattern) designed for OLTP would perform poorly when used for querying/reporting – simply because it [...]</description>
		<content:encoded><![CDATA[<p>[...] separately was accepted. Secondly, I proposed that an object model (specifically implementing the Domain Model pattern) designed for OLTP would perform poorly when used for querying/reporting – simply because it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Lazy-Loading and How Messaging Fixes Everything Again</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1451</link>
		<dc:creator>&#187; Lazy-Loading and How Messaging Fixes Everything Again</dc:creator>
		<pubDate>Sat, 21 Apr 2007 18:04:17 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1451</guid>
		<description>[...] XML/Relational Mapping as Jesse suggest here (although he ignores the whole issue of implementing Domain Models or Active Records using an O/R Mapper). What this solution enables us to do is to define different [...]</description>
		<content:encoded><![CDATA[<p>[...] XML/Relational Mapping as Jesse suggest here (although he ignores the whole issue of implementing Domain Models or Active Records using an O/R Mapper). What this solution enables us to do is to define different [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Thoughts about workflow foundation</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1449</link>
		<dc:creator>&#187; Thoughts about workflow foundation</dc:creator>
		<pubDate>Sat, 21 Apr 2007 17:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1449</guid>
		<description>[...] the business logic of the system with WF. Personally, I think that that&#8217;s a bad choice. Object-oriented domain models do an excellent job of modelling complex business logic. The procedure-oriented nature of workflows [...]</description>
		<content:encoded><![CDATA[<p>[...] the business logic of the system with WF. Personally, I think that that&#8217;s a bad choice. Object-oriented domain models do an excellent job of modelling complex business logic. The procedure-oriented nature of workflows [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Object/Relational Mapping and Scalability</title>
		<link>http://www.udidahan.com/2007/04/21/domain-model-pattern/comment-page-1/#comment-1446</link>
		<dc:creator>&#187; Object/Relational Mapping and Scalability</dc:creator>
		<pubDate>Sat, 21 Apr 2007 14:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/04/21/domain-model-pattern/#comment-1446</guid>
		<description>[...] never stand alone. They are used to provide persistence for something else &#8211; either for the Domain Model Pattern or for the Active Record [...]</description>
		<content:encoded><![CDATA[<p>[...] never stand alone. They are used to provide persistence for something else &ndash; either for the Domain Model Pattern or for the Active Record [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
