<?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: Architectural Styles</title>
	<atom:link href="http://shapingsoftware.com/2009/02/09/architectural-styles/feed/" rel="self" type="application/rss+xml" />
	<link>http://shapingsoftware.com/2009/02/09/architectural-styles/</link>
	<description>Patterns and Practices for Software Success.</description>
	<pubDate>Sat, 04 Feb 2012 12:21:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: My architecture Series &#171; Arvindsoni&#8217;s belog</title>
		<link>http://shapingsoftware.com/2009/02/09/architectural-styles/comment-page-1/#comment-51204</link>
		<dc:creator>My architecture Series &#171; Arvindsoni&#8217;s belog</dc:creator>
		<pubDate>Sat, 02 May 2009 08:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/02/09/architectural-styles/#comment-51204</guid>
		<description>[...] My architecture&#160;Series By Soni  architecture Definition  Architectural-styles/ [...]</description>
		<content:encoded><![CDATA[<p>[...] My architecture&nbsp;Series By Soni  architecture Definition  Architectural-styles/ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J.D. Meier</title>
		<link>http://shapingsoftware.com/2009/02/09/architectural-styles/comment-page-1/#comment-45501</link>
		<dc:creator>J.D. Meier</dc:creator>
		<pubDate>Fri, 27 Mar 2009 02:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/02/09/architectural-styles/#comment-45501</guid>
		<description>@ Raju

Thank you.  

On layers, just think of them as logical separation of concerns and to help enforce single responsibility.  Also, remember they are fractal (e.g. a service can be made up of multiple layers).  The common confusion around layers is mixing them with physical separation (tiers) or only using monolithic layers.  Don't use layers for layers sake, but many solutions are in fact layered architectures.

That's a good question and I'm not sure what the normal channels are beyond what you find in books, forums, blogs and trade journals.</description>
		<content:encoded><![CDATA[<p>@ Raju</p>
<p>Thank you.  </p>
<p>On layers, just think of them as logical separation of concerns and to help enforce single responsibility.  Also, remember they are fractal (e.g. a service can be made up of multiple layers).  The common confusion around layers is mixing them with physical separation (tiers) or only using monolithic layers.  Don&#8217;t use layers for layers sake, but many solutions are in fact layered architectures.</p>
<p>That&#8217;s a good question and I&#8217;m not sure what the normal channels are beyond what you find in books, forums, blogs and trade journals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raju Joseph</title>
		<link>http://shapingsoftware.com/2009/02/09/architectural-styles/comment-page-1/#comment-45391</link>
		<dc:creator>Raju Joseph</dc:creator>
		<pubDate>Thu, 26 Mar 2009 15:05:23 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2009/02/09/architectural-styles/#comment-45391</guid>
		<description>Great article. One doubt. Being a solution architect for a while now, I have noticed that most of the architecture proposed for business solution primarily follows a Layered Architectural Style (at a high level). Further, if I ask any architect to propose a solution, 99% of them follows the same Layered Architectural Style. What are your thoughts?

Further, I am curious, does any one at Microsoft (including yourself) do any outside architecture mentoring?</description>
		<content:encoded><![CDATA[<p>Great article. One doubt. Being a solution architect for a while now, I have noticed that most of the architecture proposed for business solution primarily follows a Layered Architectural Style (at a high level). Further, if I ask any architect to propose a solution, 99% of them follows the same Layered Architectural Style. What are your thoughts?</p>
<p>Further, I am curious, does any one at Microsoft (including yourself) do any outside architecture mentoring?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

