<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Research and Fabricated Complexity</title><link>http://blogs.msdn.com/annali/archive/2006/11/26/research-and-fabricated-complexity.aspx</link><description>I had the privelege to meet Willy Zwaenepoel on Thursday at a USyd seminar . He is one of the distributed systems engineering legends that I really looked up to during my PhD research days, and heavily referenced his great works. He was not only an inspirational</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Research and Fabricated Complexity</title><link>http://blogs.msdn.com/annali/archive/2006/11/26/research-and-fabricated-complexity.aspx#1184448</link><pubDate>Fri, 01 Dec 2006 17:22:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1184448</guid><dc:creator>NickMalik</dc:creator><description>&lt;p&gt;It's more than design by contract.&lt;/p&gt;
&lt;p&gt;It's Responsibilited Driven Architecture. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Design by contract is a simple tactic for partitioning but it doesn't tell you &amp;quot;why&amp;quot; or &amp;quot;where&amp;quot; to partition. &amp;nbsp;It answers more of the question of &amp;quot;how.&amp;quot; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;The key nugget of simplicity comes from collecting cohesive responsibilities into autonomous and relatively stable components, wrap them in services, and either evangelizing or governing to make sure that these key services move to the center of the application infrastructure. &amp;nbsp;Real change, towards simplicity, requires all three.&lt;/p&gt;
</description></item></channel></rss>