<?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: CQRS is not an Architecture</title>
	<atom:link href="http://goodenoughsoftware.net/2012/09/09/cqrs-is-not-an-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://goodenoughsoftware.net/2012/09/09/cqrs-is-not-an-architecture/</link>
	<description>Good Enough Software is By Definition Good Enough</description>
	<lastBuildDate>Tue, 09 Apr 2013 15:17:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Szymon Pobiega</title>
		<link>http://goodenoughsoftware.net/2012/09/09/cqrs-is-not-an-architecture/#comment-320</link>
		<dc:creator><![CDATA[Szymon Pobiega]]></dc:creator>
		<pubDate>Tue, 11 Sep 2012 03:39:23 +0000</pubDate>
		<guid isPermaLink="false">https://gregfyoung.wordpress.com/?p=326#comment-320</guid>
		<description><![CDATA[How about a single stand-alone system that does not integrate with other enterprise apps? Can we talk about architecture of such system or is it &#039;just design&#039;? If so, then SOA or EDA does not apply to it and being CQRS may be a one of the most important fact about this system&#039;s design, right?

Regarding these &#039;systems of systems&#039; I agree that patterns are about internal structure (boxes) while styles are about communication (lines).]]></description>
		<content:encoded><![CDATA[<p>How about a single stand-alone system that does not integrate with other enterprise apps? Can we talk about architecture of such system or is it &#8216;just design&#8217;? If so, then SOA or EDA does not apply to it and being CQRS may be a one of the most important fact about this system&#8217;s design, right?</p>
<p>Regarding these &#8216;systems of systems&#8217; I agree that patterns are about internal structure (boxes) while styles are about communication (lines).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slaweksobotka</title>
		<link>http://goodenoughsoftware.net/2012/09/09/cqrs-is-not-an-architecture/#comment-314</link>
		<dc:creator><![CDATA[slaweksobotka]]></dc:creator>
		<pubDate>Sun, 09 Sep 2012 13:10:26 +0000</pubDate>
		<guid isPermaLink="false">https://gregfyoung.wordpress.com/?p=326#comment-314</guid>
		<description><![CDATA[Imho: depends on semantics.
W can consider different &quot;levels&quot; of Architecture (all are important):
1. Application Architecture - now to structure code (responsibility) in one &quot;module&quot; of whole system.
Application architectures ex:
- layers (not tiers, different layers)
- microcernel
- ports&amp;adapters (imho it&#039;s unification of Layers + P&amp;A + Pipes&amp;Filters)
- CqRS - hmmm can be used as separate Application Arch (or as inner structure of P&amp;A &quot;hexagon&quot;)
- ... ?
2. System Architecture - how to structure (encapsulate and integrate) &quot;modules&quot; in bigger &quot;universe&quot;
You mentioned:
- SOA
- EDA (Pipes&amp;Filters?)
- ...?
3. Deployment, Security, Scalability,... Architectures

According to this semantics ES is imho &quot;just&quot; a persistence technique.

This is just my private &quot;mental scaffolding&quot; that helps to grasp and categorize ideas.
What do You think about this approach to looking at different &quot;zoom levels&quot;?

regards
Sławek Sobótka]]></description>
		<content:encoded><![CDATA[<p>Imho: depends on semantics.<br />
W can consider different &#8220;levels&#8221; of Architecture (all are important):<br />
1. Application Architecture &#8211; now to structure code (responsibility) in one &#8220;module&#8221; of whole system.<br />
Application architectures ex:<br />
- layers (not tiers, different layers)<br />
- microcernel<br />
- ports&amp;adapters (imho it&#8217;s unification of Layers + P&amp;A + Pipes&amp;Filters)<br />
- CqRS &#8211; hmmm can be used as separate Application Arch (or as inner structure of P&amp;A &#8220;hexagon&#8221;)<br />
- &#8230; ?<br />
2. System Architecture &#8211; how to structure (encapsulate and integrate) &#8220;modules&#8221; in bigger &#8220;universe&#8221;<br />
You mentioned:<br />
- SOA<br />
- EDA (Pipes&amp;Filters?)<br />
- &#8230;?<br />
3. Deployment, Security, Scalability,&#8230; Architectures</p>
<p>According to this semantics ES is imho &#8220;just&#8221; a persistence technique.</p>
<p>This is just my private &#8220;mental scaffolding&#8221; that helps to grasp and categorize ideas.<br />
What do You think about this approach to looking at different &#8220;zoom levels&#8221;?</p>
<p>regards<br />
Sławek Sobótka</p>
]]></content:encoded>
	</item>
</channel>
</rss>
