<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Introduction to Service-Oriented Architecture</title>
	<link>http://www.linux-mag.com/id/3387/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sun, 07 Sep 2008 01:02:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: tizzyd</title>
		<link>http://www.linux-mag.com/id/3387/#comment-213</link>
		<pubDate>Sat, 21 Jul 2007 14:10:16 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/3387/#comment-213</guid>
					<description>I have been disappointed with the direction web services in particular and SOA in general has gone.  More and more complexity, more and more bulk.  A recent comparison I did at a client site showed that the SOAP message was nearly 20K, whereas the REST message (using a much simpler XML-RPC schema) was only about 2K.  In this case, the 90% bloat did not provide them with any value.  It took longer to develop.  The toolsets were more expensive, and the resources to engineer the solution were more costly.  In fact, because of the complexity, the developers uses really did not understand what they were doing...they just followed the wizards.

Bloat, complexity for little to no demonstrated value, and more costly . . . sounds like a great solution for hardware manufacturers and service companies.  Wait, just how do Sun and IBM make their money?</description>
		<content:encoded><![CDATA[<p>I have been disappointed with the direction web services in particular and SOA in general has gone.  More and more complexity, more and more bulk.  A recent comparison I did at a client site showed that the SOAP message was nearly 20K, whereas the REST message (using a much simpler XML-RPC schema) was only about 2K.  In this case, the 90% bloat did not provide them with any value.  It took longer to develop.  The toolsets were more expensive, and the resources to engineer the solution were more costly.  In fact, because of the complexity, the developers uses really did not understand what they were doing&#8230;they just followed the wizards.</p>
<p>Bloat, complexity for little to no demonstrated value, and more costly . . . sounds like a great solution for hardware manufacturers and service companies.  Wait, just how do Sun and IBM make their money?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lee McKusick</title>
		<link>http://www.linux-mag.com/id/3387/#comment-60</link>
		<pubDate>Fri, 01 Jun 2007 00:51:17 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/3387/#comment-60</guid>
					<description>Service Oriented Architecture (SOA) has the tone and feel of a grand unifying idea for business system designs and programming.

Ruby on Rails strikes me as a programming system that fits right into SOA. 

Rails divides the application into Model, View and Controller. Writing  multiple Views is a lot like re-implementing multiple Services in the SOA narrative. 

Where I think open source applications do not have the power required for an SOA project is tools for  developing Unified Modeling Language (UML). 

I thought of UML as a tool for designing multiple interacting databases and program pseudo code. SOA clearly requires a coherent core data design. (Or at least different databases linked in a usable way.) The main consultancy that developed UML was bought by IBM somewhere around 2001. 

I hope followup articles develop a bigger and better picture of how to use SOA, especially in an open source setting. Grand unifiying ideas require  applications and programming environments don't they?</description>
		<content:encoded><![CDATA[<p>Service Oriented Architecture (SOA) has the tone and feel of a grand unifying idea for business system designs and programming.</p>
<p>Ruby on Rails strikes me as a programming system that fits right into SOA. </p>
<p>Rails divides the application into Model, View and Controller. Writing  multiple Views is a lot like re-implementing multiple Services in the SOA narrative. </p>
<p>Where I think open source applications do not have the power required for an SOA project is tools for  developing Unified Modeling Language (UML). </p>
<p>I thought of UML as a tool for designing multiple interacting databases and program pseudo code. SOA clearly requires a coherent core data design. (Or at least different databases linked in a usable way.) The main consultancy that developed UML was bought by IBM somewhere around 2001. </p>
<p>I hope followup articles develop a bigger and better picture of how to use SOA, especially in an open source setting. Grand unifiying ideas require  applications and programming environments don&#8217;t they?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Deutschmann</title>
		<link>http://www.linux-mag.com/id/3387/#comment-35</link>
		<pubDate>Thu, 31 May 2007 18:46:09 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/3387/#comment-35</guid>
					<description>Has any technology or project ever started with the intention of producing a whole that is less than the sum of the parts, or even just equal to the sum of the parts?

And yet, here we are....</description>
		<content:encoded><![CDATA[<p>Has any technology or project ever started with the intention of producing a whole that is less than the sum of the parts, or even just equal to the sum of the parts?</p>
<p>And yet, here we are&#8230;.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
