On 29 Jun 2008, at 16:03, Rob Eamon wrote:
>> <<Best Practices for SOA: Building a Data Services Layer
>>
>> If businesses are to have any hope of building flexible services that
>> offer the performance and agility needed to succeed with SOA, those
>> businesses must solve the technical challenge of accessing
>> information – that is, data – across application platforms and their
>> organization as a whole.
>
> I disagree. The challenge in an SO approach is *not* to gain access to
> data within legacy applications. (That would be a data oriented
> approach--and, as it happens, a typical old-school integration
> approach). An SO approach would strive to extract and leverage
> *services* from legacy applications. Or at least capabilities that
> would be an implementation component of a service implementation.
Exactly. We want the behavior of the existing applications. How
they implement that behavior is of little to no interest.
Regards,
Patrick
----
[EMAIL PROTECTED]
S P Engineering, Inc.
Large scale, mission-critical, distributed OO systems design and
implementation.
(C++, Java, Common Lisp, Jini, middleware, SOA)
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
