<?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: The Monolith</title>
	<atom:link href="http://lostechies.com/evanhoff/2008/01/10/the-monolith/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/evanhoff/2008/01/10/the-monolith/</link>
	<description>Just another LosTechies site</description>
	<lastBuildDate>Thu, 11 Sep 2008 15:52:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Fernando</title>
		<link>http://lostechies.com/evanhoff/2008/01/10/the-monolith/#comment-64</link>
		<dc:creator>Fernando</dc:creator>
		<pubDate>Thu, 10 Jan 2008 12:52:24 +0000</pubDate>
		<guid isPermaLink="false">/blogs/evan_hoff/archive/2008/01/09/the-monolith.aspx#comment-64</guid>
		<description>Nice post.
Then, the natural question follows: How do we architect non-monolithic systems ?

The newest round of technologies such as WCF, LINQ (especially LINQ to SQL), and ADO.NET Data Services promote and enable non-monolithism. However, it seems that everyone and their brother (not your case) blogs and/or writes books on the technologies for the technologies sake.
What&#039;s missing are examples of the design of simple, end-to-end systems that leverage decoupling/non-monolithism with these modern technologies.
I haven&#039;t found yet any books/blog posts/MSDN articles targeted at the independent developer (e.g. Micro ISV), freelance IT consultant or architect that &quot;coaches&quot; him throughout the thought process required for the successful design and implementation of such non-monolithic solutions.

What would you recommend ?
Thanks.

Cheers.
</description>
		<content:encoded><![CDATA[<p>Nice post.<br />
Then, the natural question follows: How do we architect non-monolithic systems ?</p>
<p>The newest round of technologies such as WCF, LINQ (especially LINQ to SQL), and ADO.NET Data Services promote and enable non-monolithism. However, it seems that everyone and their brother (not your case) blogs and/or writes books on the technologies for the technologies sake.<br />
What&#8217;s missing are examples of the design of simple, end-to-end systems that leverage decoupling/non-monolithism with these modern technologies.<br />
I haven&#8217;t found yet any books/blog posts/MSDN articles targeted at the independent developer (e.g. Micro ISV), freelance IT consultant or architect that &#8220;coaches&#8221; him throughout the thought process required for the successful design and implementation of such non-monolithic solutions.</p>
<p>What would you recommend ?<br />
Thanks.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mickael</title>
		<link>http://lostechies.com/evanhoff/2008/01/10/the-monolith/#comment-63</link>
		<dc:creator>Mickael</dc:creator>
		<pubDate>Thu, 10 Jan 2008 12:09:19 +0000</pubDate>
		<guid isPermaLink="false">/blogs/evan_hoff/archive/2008/01/09/the-monolith.aspx#comment-63</guid>
		<description>&quot;Must be versioned and deployed as a whole &quot;...sounds ok. BTW Versioning is a tricky part for distributed systems. </description>
		<content:encoded><![CDATA[<p>&#8220;Must be versioned and deployed as a whole &#8220;&#8230;sounds ok. BTW Versioning is a tricky part for distributed systems. </p>
]]></content:encoded>
	</item>
</channel>
</rss>
