<?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: What&#8217;s an ESB architecture!?</title>
	<atom:link href="http://www.richardhallgren.com/whats-an-esb-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardhallgren.com/whats-an-esb-architecture/</link>
	<description>.NET, BizTalk and integration focused scribbles</description>
	<lastBuildDate>Tue, 01 Jun 2010 22:09:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard</title>
		<link>http://www.richardhallgren.com/whats-an-esb-architecture/comment-page-1/#comment-57</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Wed, 25 Jul 2007 06:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardhallgren.com/?p=48#comment-57</guid>
		<description>@David: I know what you mean ...

I think it&#039;s important to separate the concept and idea behind a &lt;b&gt;bus architecture&lt;/b&gt; and a &lt;b&gt;&quot;bus product&quot;&lt;/b&gt;.

I think most get the idea and pros behind a bus architecture on a high level (all messages travel through one bus that we can monitor and configure etc, etc). Basically we get another level of control over the services within the enterprise (sure there is more to it but to me this is the essence). This is a abstract architectural &lt;b&gt;concept&lt;/b&gt;.

However when it comes to products I struggle to identify what&#039;s a &quot;ESB product&quot; and what isn&#039;t. I found &lt;a href=&quot;http://seroter.wordpress.com/2007/05/14/biztalk-server-and-soa-software-together-part-i/&quot; rel=&quot;nofollow&quot;&gt;Richard S&#039;s series of post on the SOA software&lt;/a&gt; very interesting - is it in the ESB ballpark? I also looked at the &lt;a href=&quot;http://www.neudesic.com/Media/Neudesic%20-%20Neuron%20ESB%20Brochure.pdf&quot; rel=&quot;nofollow&quot;&gt;broshyre for Neuron&lt;/a&gt; and it explains a bit more in detail (there&#039;s even a couple of scrrenshoots) what their ESB product does ...

I hope this helps some ... Let me know.</description>
		<content:encoded><![CDATA[<p>@David: I know what you mean &#8230;</p>
<p>I think it&#8217;s important to separate the concept and idea behind a <b>bus architecture</b> and a <b>&#8220;bus product&#8221;</b>.</p>
<p>I think most get the idea and pros behind a bus architecture on a high level (all messages travel through one bus that we can monitor and configure etc, etc). Basically we get another level of control over the services within the enterprise (sure there is more to it but to me this is the essence). This is a abstract architectural <b>concept</b>.</p>
<p>However when it comes to products I struggle to identify what&#8217;s a &#8220;ESB product&#8221; and what isn&#8217;t. I found <a href="http://seroter.wordpress.com/2007/05/14/biztalk-server-and-soa-software-together-part-i/" rel="nofollow">Richard S&#8217;s series of post on the SOA software</a> very interesting &#8211; is it in the ESB ballpark? I also looked at the <a href="http://www.neudesic.com/Media/Neudesic%20-%20Neuron%20ESB%20Brochure.pdf" rel="nofollow">broshyre for Neuron</a> and it explains a bit more in detail (there&#8217;s even a couple of scrrenshoots) what their ESB product does &#8230;</p>
<p>I hope this helps some &#8230; Let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.richardhallgren.com/whats-an-esb-architecture/comment-page-1/#comment-56</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 24 Jul 2007 22:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardhallgren.com/?p=48#comment-56</guid>
		<description>What I find interesting is that these kinds of attempts to explain what an ESB is always put up diagrams of the &quot;old&quot; models: point-to-point, hub-spoke, and message-bus; but they never put up a diagram of an ESB. They go through pages and pages of text attempting to explain it, when all I want is one simple diagram. As it is, I have read dozens of whitepapers from vendors and bloggers and technologists all over the web, and I still don&#039;t have a clue what an ESB is supposed to be.</description>
		<content:encoded><![CDATA[<p>What I find interesting is that these kinds of attempts to explain what an ESB is always put up diagrams of the &#8220;old&#8221; models: point-to-point, hub-spoke, and message-bus; but they never put up a diagram of an ESB. They go through pages and pages of text attempting to explain it, when all I want is one simple diagram. As it is, I have read dozens of whitepapers from vendors and bloggers and technologists all over the web, and I still don&#8217;t have a clue what an ESB is supposed to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.richardhallgren.com/whats-an-esb-architecture/comment-page-1/#comment-55</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Mon, 23 Jul 2007 14:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardhallgren.com/?p=48#comment-55</guid>
		<description>In my mind BizTalk has been close to an ESB for quite a while and from what I&#039;ve seen the ESB project can make it go all the way. Especially when it comes to areas like configuration and management that I see as it main weaknesses today and that the ESB guidance package has cool solutions for.

I&#039;m very much looking forward for the ESB guidance project to be more available than it is in the current CTP (I&#039;m talking webcasts and documentation etc here)!</description>
		<content:encoded><![CDATA[<p>In my mind BizTalk has been close to an ESB for quite a while and from what I&#8217;ve seen the ESB project can make it go all the way. Especially when it comes to areas like configuration and management that I see as it main weaknesses today and that the ESB guidance package has cool solutions for.</p>
<p>I&#8217;m very much looking forward for the ESB guidance project to be more available than it is in the current CTP (I&#8217;m talking webcasts and documentation etc here)!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RyanElee</title>
		<link>http://www.richardhallgren.com/whats-an-esb-architecture/comment-page-1/#comment-54</link>
		<dc:creator>RyanElee</dc:creator>
		<pubDate>Mon, 23 Jul 2007 13:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardhallgren.com/?p=48#comment-54</guid>
		<description>Great, Thanks for your contribution.

Do you think the micrsoft ESB guidance CTP achieve the demand of ESB?</description>
		<content:encoded><![CDATA[<p>Great, Thanks for your contribution.</p>
<p>Do you think the micrsoft ESB guidance CTP achieve the demand of ESB?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
