[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm-ra] Registries and Repositories
Danny: Thanks. In addition to working on some of the standards and architectures for registry-repository, I have worked in two companies that built such beasts including Yellow Dragon Software who was acquired for the Registry-Repository software by my current employer Adobe Systems. Matt is the lead architect on making sure our service registry is properly implemented in LiveCycle to facilitate our services layer. http://technoracle.blogspot.com/2006/08/adobe-livecycle-8-gets-soa-right.htm l Duane On 12/4/06 9:40 PM, "Danny Thornton" <danny_thornton2@yahoo.com> wrote: > The registry does store some data along with > meta-data. For example, UDDI stores data for the > businessEntity, businessService, bindingTemplate, and > tModel. The tModel itself can be meta-data. > > I looked at your slides Duane (Justice Registry > Prototype Use Case) and I like the way you represented > the Logical Data Model in the registry. Your slides > have given me an answer to an Information Model > problem I am working on at work. I also took a look > at your racing video. Next time you are video taping > in your Porsche, how about a power slide for us. A > take down of all those cones at the end would have > been really impressive. > > I see a distinction between registry and repository > that I prefer and I don't think it is too > controversial to what others are thinking. > > Danny > > --- Duane Nickull <dnickull@adobe.com> wrote: > >> Service Registries act as pointers to metadata that >> describe the service. >> They fulfill many aspects of the SOA metamodel >> including the visibility (by >> making the service endpoints findable to the >> consumer), pointing at >> artifacts that contain the metadata for things like >> the service policy, the >> service description and other things. Holding the >> code that makes the >> service run is not something one would normally >> employ a registry/repository >> for. >> >> The repository is not as simple as it at first >> seems. Many people have a >> perception that a repository is one "thing" when in >> fact, the artifacts >> might be de-centralized. For example, the registry >> might hold a static copy >> of a WSDL in resident memory via an internal >> repository, but it might point >> at an extrinsic artifact for the service policy >> which resides on a different >> system. While this is nice in terms of a dynamic >> system that can facilitate >> some aspects of late binding (simple changes like >> ports, URL's, SOAP >> versions etc.), it also introduces a problem of >> synchronization between the >> registry and the repository. The registry might not >> be notified if an >> extrinsic objects changes state. This could be >> solved using a mechanism >> like WS-Eventing. >> >> I have many sets of slides available for download at >> www.nickull.net on the >> subject (including ISO 11179, UDDI and ebXML >> Registry) if anyone wants to >> read up on the topic. >> >> Duane >> >> >> On 12/4/06 8:09 AM, "Chiusano, Joseph" >> <chiusano_joseph@bah.com> wrote: >> >>> More thoughts: >>> >>> So the registry would store metadata that >> describes service artifacts, >>> which are stored in a repository. Service >> artifacts can also be >>> considered types of IT artifacts. >>> >>> Joe >>> >>> Joseph Chiusano >>> Associate >>> >>> Booz | Allen | Hamilton >>> ______________________-- >>> >>> 700 13th St. NW, Suite 1100 >>> Washington, DC 20005 >>> O: 202-508-6514 >>> C: 202-251-0731 >>> Visit us online@ http://www.boozallen.com >>> >>> -----Original Message----- >>> From: Chiusano, Joseph >> [mailto:chiusano_joseph@bah.com] >>> Sent: Monday, December 04, 2006 10:41 AM >>> To: Danny Thornton; Francis McCabe >>> Cc: soa-rm-ra@lists.oasis-open.org >>> Subject: RE: [soa-rm-ra] Registries and >> Repositories >>> >>> To me, a service description is one example of a >> service artifact. A >>> service policy in text form (for human >> consumption) would be another >>> example. If I recall correctly, a service policy >> in electronic form >>> would be part of the service description according >> to our RM (if I am >>> not correct, then that would be another example of >> a service artifact). >>> >>> Joe >>> >>> Joseph Chiusano >>> Associate >>> >>> Booz | Allen | Hamilton >>> ______________________-- >>> >>> 700 13th St. NW, Suite 1100 >>> Washington, DC 20005 >>> O: 202-508-6514 >>> C: 202-251-0731 >>> Visit us online@ http://www.boozallen.com >>> >>> -----Original Message----- >>> From: Danny Thornton >> [mailto:danny_thornton2@yahoo.com] >>> Sent: Monday, December 04, 2006 10:16 AM >>> To: Chiusano, Joseph; Francis McCabe >>> Cc: soa-rm-ra@lists.oasis-open.org >>> Subject: RE: [soa-rm-ra] Registries and >> Repositories >>> >>> So let's expand on what a service artifact is and >> what a service >>> description artifact is. This will help provide a >> better distinction >>> between the registry and the repository. >>> >>> Danny >>> >>> >>> --- "Chiusano, Joseph" <chiusano_joseph@bah.com> >>> wrote: >>> >>>> Suggestion: The repository is the storage >> location for service >>>> artifacts. >>>> >>>> Joseph Chiusano >>>> Associate >>>> >>>> Booz | Allen | Hamilton >>>> ______________________-- >>>> >>>> 700 13th St. NW, Suite 1100 >>>> Washington, DC 20005 >>>> O: 202-508-6514 >>>> C: 202-251-0731 >>>> Visit us online@ http://www.boozallen.com >>>> >>>> -----Original Message----- >>>> From: Francis McCabe [mailto:frankmccabe@mac.com] >>>> Sent: Monday, December 04, 2006 1:00 AM >>>> To: Danny Thornton >>>> Cc: soa-rm-ra@lists.oasis-open.org >>>> Subject: Re: [soa-rm-ra] Registries and >> Repositories >>>> >>>> We can certainly discuss this. >>>> However, I am not sure that I see everything >> here. >>>> For one thing, I do not see how services can be >> stored... >>>> >>>> Frank >>>> >>>> On Dec 3, 2006, at 9:31 PM, Danny Thornton wrote: >>>> >>>>> I would like to add a Registry/Repository >>>> discussion to the agenda for >>>> >>>>> this Wednesday RM providing we have time. This >>>> relates to the >>>>> Visibility section of the RA. >>>>> >>>>> >>>> >>> >> > http://wiki.oasis-open.org/soa-rm/TheArchitecture/ServiceView/ >>>>> Visibility >>>>> >>>>> The RA currently defines the registry as >>>> containing links to Service >>>>> Description artifacts and the repository is >>>> defined as storing those >>>>> artifacts. >>>>> >>>>> Another view of the repository is that the >>>> repository is the storage >>>>> location for the services, the system of record >> of >>>> the services. One >>>>> of the things stored in the repository is the >>>> configuration management >>>> >>>>> of the SOA service code. In this view, the SOA >>>> repository becomes >>>>> somewhat internal to the organization. The >>>> majority of the Service >>>>> Description and its artifacts reside in the >>>> service registry. >>>>> >>>>> Other thoughts on this? >>>>> >>>>> Danny >>>>> >>>>> >> __________________________________________________ >>>>> Do You Yahoo!? >>>>> Tired of spam? Yahoo! Mail has the best spam >> > === message truncated === > > > > > ______________________________________________________________________________ > ______ > Yahoo! Music Unlimited > Access over 1 million songs. > http://music.yahoo.com/unlimited -- ********************************************************** Sr. Technical Evangelist - Adobe Systems, Inc. * Chair - OASIS SOA Reference Model Technical Committee * Blog: http://technoracle.blogspot.com * Music: http://www.mix2r.com/audio/by/artist/duane_nickull* **********************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]