Todd Biske wrote:
Phil Wainewright posted a great article on his Loosely Coupled blog.
Here's an excerpt:
Early adopters more or less stumbled upon the need for a
repository, without at first realizing just how crucial it was going to
be. Recognition of the role of the repository went through three phases:
- Denial . Originally, it was
thought that a registry, based on the UDDI standard, would be
sufficient: Services would just use the registry to seek out matching
resources at runtime and consume them automagically. But this early
vision failed to take into account issues like contracts, shared
meaning, reputation and trust.
- Awareness . As enterprises
began to build SOAs that linked services from different domains, it
became obvious there was a need for some kind of system of record that
developers could consult at design time. This would have to provide
more information than a barebones UDDI registry was equipped for, and
indeed taking into account the need to include documentation and other
supporting material, it became evident that the directory-like registry
model didn't go far enough. There needed to be some kind of document
store with its own defined processes, in other words, a repository.
- Acceptance . The more one
started to think about what one could do with a repository, the more
obvious it became how necessary it was to have one. Not just at design
time, but also through deployment, runtime, and on to change
time — those moments when a live service needs to
adjust to changing circumstances.
+1
The following paper talks about the importance of a standards-based,
integrated registry-repository:
SOA Registry Repository White Paper:
<http://www.sun.com/products/soa/registry/soa_registry_wp.pdf>
-
The one opportunity that Phil didn't take in this article was to
make the connection between this and Web 2.0. I've put up a post on
this in my blog, but in short, I learned a long time ago that achieving
reuse at an enterprise scale was all about marketing and
communication. The trend toward SOA repositories, combined with case
studies like Verizon, may have just created the opportunity to bring
elements of Web 2.0 into the corporate IT world.
+1
I see a lot of application for standards-based, integrated
registry-repository to enable and support various aspects of web 2.
For those not familiar with Web 2.0 concept here is a link:
http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html
--
Regards,
Farrukh
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
begin:vcard
fn:Farrukh Najmi
n:Najmi;Farrukh
email;internet:[EMAIL PROTECTED]
tel;work:781-442-9017
url:http://ebxmlrr.sourceforge.net/tmp/farrukhRacePointIcon.jpg
version:2.1
end:vcard
