<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>service-orientated-architecture at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/</link>
    <description>SOA</description>

    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 22:08:20 GMT</pubDate>
      <dc:creator>Hitoshi Ozawa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13555</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13555</guid>
      <description>... If you&#39;re comparing with OO, I think you mean SO instead of SOA. I was against &quot;killing&quot; SOA because just &quot;service&quot; tends to make it sound more like a</description>
    </item>
    <item>
      <title>ZapForum Boston: &quot;SOA: The Night of the Living Dead&quot; Evening Network</title>
      <pubDate>Fri, 03 Jul 2009 19:39:26 GMT</pubDate>
      <dc:creator>zapthinkllc</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13554</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13554</guid>
      <description>Greetings to you all! On July 23, 2009 dozens of experts, pundits, and influential guests will gather in Boston, MA for an evening of networking and discussion</description>
    </item>
    <item>
      <title>Re: Michelson on Service Re-Use et al.</title>
      <pubDate>Fri, 03 Jul 2009 19:38:37 GMT</pubDate>
      <dc:creator>Rob Eamon</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13553</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13553</guid>
      <description>... At the architecture defintion of a service component, what makes up the interface definition of that component? IMO, operations and the data/messages</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 15:45:34 GMT</pubDate>
      <dc:creator>Chris Deweese</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13552</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13552</guid>
      <description>Anne, I will try to be much more cautious with my context.  I see that it is pretty easy on this list to leave enough out to send across the wrong meaning.  I</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 14:05:12 GMT</pubDate>
      <dc:creator>Anne Thomas Manes</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13551</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13551</guid>
      <description>Chris, I disagree with your assertion that SOA should not be used for &quot;throw-away&quot; projects. SOA principles should be applied to all projects to ensure</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 14:04:51 GMT</pubDate>
      <dc:creator>Marcelo A. Costa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13550</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13550</guid>
      <description>When I wrote &quot;SOA middleware&quot; I meant middleware used for SOA solutions. And I do not mean SOA is only this middleware or topology, although some good</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 14:04:20 GMT</pubDate>
      <dc:creator>Hitoshi Ozawa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13549</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13549</guid>
      <description>Arggggg!  &quot;available hardware&quot;? ... good experience on creating a guideline to how a service interacts on an architecture and a good experience on a way of</description>
    </item>
    <item>
      <title>Re: Udi on the Fallacy of Reuse</title>
      <pubDate>Fri, 03 Jul 2009 14:04:16 GMT</pubDate>
      <dc:creator>Michael Poulin</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13548</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13548</guid>
      <description>Yes, I agree especially with maintenance cost. To fight this problem with business, I used to calculate not the cost of the project but the cost of the</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 02:24:53 GMT</pubDate>
      <dc:creator>Chris Deweese</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13547</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13547</guid>
      <description>Hi GV, Sorry I over-simplified your question, my apologies.  I think there would be plenty of non-functional reasons, such as available hardware, scope of</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 01:49:54 GMT</pubDate>
      <dc:creator>Michael Poulin</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13546</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13546</guid>
      <description>I think that the question need to be re-phrased, GV. What is &#39;non functional&#39;s&#39; if you want to work with functions (i.e. with SOA)? You have to distinguish</description>
    </item>
    <item>
      <title>Re: Udi on the Fallacy of Reuse</title>
      <pubDate>Fri, 03 Jul 2009 01:46:40 GMT</pubDate>
      <dc:creator>htshozawa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13545</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13545</guid>
      <description>You&#39;re totally right, but is there any simple way to measure &quot;reused&quot; service and &quot;used&quot; service with your definition? Measurements are good to calculate ROI. </description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 00:58:27 GMT</pubDate>
      <dc:creator>Anne Thomas Manes</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13544</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13544</guid>
      <description>I think it depends on your definition of &quot;SOA&quot;. By my definition, SOA is a set of design principles. From my perspective, you should always keep those design</description>
    </item>
    <item>
      <title>Re: Udi on the Fallacy of Reuse</title>
      <pubDate>Fri, 03 Jul 2009 00:56:47 GMT</pubDate>
      <dc:creator>A W</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13543</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13543</guid>
      <description>What about the following example about re-use: A service to obtain a customer?s status that can be called by any other application within the organization or</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 00:54:27 GMT</pubDate>
      <dc:creator>Michael Poulin</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13542</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13542</guid>
      <description>Disagree, there is no such thing as &#39;SOA middleware&#39;; there is middelware used for SOA solutions. Any middleware hits performances but it is not a reason to</description>
    </item>
    <item>
      <title>Re: When is SOA not applicable?</title>
      <pubDate>Fri, 03 Jul 2009 00:53:54 GMT</pubDate>
      <dc:creator>htshozawa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13541</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/service-orientated-architecture/message/13541</guid>
      <description>Oh, oh. &quot;SOA middleware&quot;? Even when performance is an issue, it&#39;s still possible to use the concept of SOA to design services and an architecture. Architecture</description>
    </item>

  </channel>
</rss>
<!-- wr2.grp.sp2.yahoo.com uncompressed/chunked Mon Jul  6 16:07:42 PDT 2009 -->
