WSDL etc (“the contract”) are the
config/design time artifacts of loosely coupled services. The loosely coupled
run-time is still not in the market. Having a loosely coupled contract running
on tightly coupled run-time will not result in an SOA.
Vikas
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Ron Schmelzer
Sent: Wednesday, September 14,
2005 7:11 AM
To:
[email protected]
Subject: [service-orientated-architecture]
ZapThink needs help: Sample contracts?
Hi All --
As you all know, one of the key parts to making
loosely coupled Services
work is a well-defined contract that identifies
both functional as well
as non-functional requirements for Service
providers and consumers. By
now, you also probably realized that WSDL by
itself is not sufficient to
provide all the metadata needed for loose coupling
and late binding.
Other metadata are needed including security,
semantics, QoS, SLA,
process, etc.
So, what we are looking for are actual examples of
real-world contracts,
or templates for contracts that you are using in
real-world SOA
deployments, or at the very least, guidance for
how those contracts can
be defined.
So, help anyone?
Thanks in advance!
Best,
Ron
--
_____________________________________________________________
Ronald Schmelzer
[EMAIL PROTECTED]
Senior Analyst
ZapThink LLC
Direct: 781-577-2779 / Main: 781-207-0203
YAHOO! GROUPS LINKS
