<?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>Architecting Service Broker Applications</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx</link><description>Architecting Service Broker Applications I signed up to do a presentation on Architecting Service Broker Applications so I thought I would write up my thinking here to see if I got any useful feedback. Pretty much all the presentations, papers, and books</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Architecting Service Broker Applications</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx#746984</link><pubDate>Sat, 09 Sep 2006 01:52:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:746984</guid><dc:creator>tomasr</dc:creator><description>&lt;P&gt;Roger, &lt;BR&gt;&lt;BR&gt;Good stuff, and very interesting to those of us who haven't had a chance to play with SSB much. Thanks for it. &lt;BR&gt;&lt;BR&gt;One suggestion, however: You give a good overview of the features in SSB and how they might be leveraged. It might be nice to have that complemented with information about what other products/technologies out there that might "compete" (or complement) with the facilities that SSB provides and how to choose from them. &lt;BR&gt;&lt;BR&gt;For example, you mention Queueing as a pretty big feature in SSB and a way to add asynchronous work to your application. Great. However, certainly MSMQ and BizTalk could be leveraged to provide queuing as well in many circumstances. What considerations would the architect give to see what the right technology here would be? &amp;nbsp; &lt;BR&gt;&lt;BR&gt;I think this might easily be the place were architects get a little bit worried, as the Microsoft platform stack is gaining a lot of overlapping functionality over the product set (i.e. WinFX, BizTalk, SQL Server, and so on), and it's getting more complex to decide on what the right feature from each product is.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Author's response:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This comment about the MSMQ positioning is rather puzzling because one of the main point of the article was to point out when Service Broker was appropriate and when it wasn't.&amp;nbsp; I also included a link to another post that deals exclusively with Service Broker positioning.&amp;nbsp; Either I totally failed to communicate one of my main points or there's something missing that I'm not aware of.&amp;nbsp; If there's something specific missing from the guidance let me know and I'll try to include it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description></item><item><title>[Blog] Architecting Service Broker Applications</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx#754587</link><pubDate>Thu, 14 Sep 2006 22:44:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:754587</guid><dc:creator>Damir Tomicic : ein Tag in der Community</dc:creator><description /></item><item><title>Architecting Service Broker applications (part 3)</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx#758388</link><pubDate>Sun, 17 Sep 2006 04:34:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:758388</guid><dc:creator>Have Data Will Travel</dc:creator><description>Architecting Service Broker applications (part 3)&lt;br&gt;&amp;amp;amp;nbsp;&lt;br&gt;This is the final installment (I promise)...</description></item><item><title>Have Data Will Travel : Architecting Service Broker Applications</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx#8577275</link><pubDate>Fri, 06 Jun 2008 11:51:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8577275</guid><dc:creator>Weddings</dc:creator><description>&lt;p&gt;Architecting Service Broker Applications I signed up to do a presentation on Architecting Service Broker Applications so I thought I would write up my thinking here to see if I got any useful feedback. Pretty much all the presentations, papers, and book&lt;/p&gt;
</description></item><item><title>Some useful tips when working with the Service Broker in SQL Server 2005</title><link>http://blogs.msdn.com/rogerwolterblog/archive/2006/09/08/Roger.aspx#8960742</link><pubDate>Mon, 22 Sep 2008 02:12:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8960742</guid><dc:creator>Microsoft SQL Server Tips &amp; Tricks</dc:creator><description>&lt;p&gt;With Service Broker, internal or external processes can send and receive guaranteed, asynchronous messages&lt;/p&gt;
</description></item></channel></rss>