This article is dedicated to the taxonomy of the Service Repository and the various ways it is used by the lightweight Service Broker for dynamic Service Compositions. The first article that was published earlier in August discussed the entities and service attributes that required looking up from different layers of service frameworks (Orchestration, Service Composition and Adapter services). Here we will examine relations between entities in repository, suitability for DB implementation and how they can be presented in the XML Message Container, which is sufficiently universal for the agnostic Service Broker.
As mentioned earlier, this practical approach bears many similarities to the more theoretical Service-Aware Interoperability Framework-Canonical Definition (SAIF CD), recently published by HL7. This approach of practical realization was presented in September at the 5th International SOA, Cloud and Service Technology Symposium. Interestingly, this topic appeared to be quite popular as OASIS, one of the open SOA standardization communities, also decided to present on the draft version of "Reference Architecture Framework for SOA". Their draft seemed quite theoretical in its mention of how its committee members were still debating on the definition of "service." When asked about the practical value of this reference model for SOA practitioners, Mr. Brown said that the purpose is "to build a better SOA." This article will employ the definition of "service" as provided by Thomas Erl and focus on the practical realization of the taxonomy of Service. We start by examining the basic artifacts, most of which were already identified when the lookup entities were counted. Everything begins with the Object, which is the most abstract entity in any hierarchy. There is quite a limited number of truly unique things on the enterprise level that are usually described during the earlier stages of a project's MDA exercises (in UML form). The transportable-or serializable-form of the Object is a Message, which is slightly less abstract but can still exist as a message "Message," commonly described as XSD. The Object does not exist alone; the Object and its context live and evolve within the application, presented as a set of components and resources that are interfaced by the API (or contract) composing a complex artifact-called a Trading Partner in old EDI times. Not exactly a SOA term, it is still capable of describing an Application, application user(s), API (contract) with related protocol(s) and interchange pattern(s) as one composite entity...
This article discusses the SOA suite offerings from present-day middleware technology giants, viz, Oracle, IBM and SAG. With so many open source and proprietary solutions available in the market, it is not unusual for solution architects to veer away from the basic needs of their EA landscape. This article provides a single point of reference for all critical components of a good and comprehensive SOA suite. It also compares the applicability of each tool, along with the pros and cons of using the entire suite in any EA landscape. The author assumes the reader is cognizant of SOA concepts, and believes that previous hands-on experience in SOA development will make this read more meaningful. This article will be most helpful for architects that have experience in at least one SOA stack and would like to broaden their exposure and knowledge to other offerings. The author of this article has been pragmatic and open about his views regarding the three stacks discussed. He expects the readers to use this article as a point of reference and/or checklist, and strongly discourages readers from treating it as a verdict. He adds that "invariably every enterprise has unique business components, talking to each other in unique compositions which in-turn requires unique integration solution(s)". Please do your own in-depth research and reverse engineering to determine which stack best addresses your integration requirements. SOA and cloud are two of the most popular topics of discussion in technology space nowadays. Irrespective of whether a discussion revolves around RIA, BI, MDM, ETL, SFDC or Big Data, etc., SOA and cloud have both become central discussion pieces. Another common denominator for both SOA and cloud is that both are fundamentally enterprise solution principles at heart and not technology solutions in themselves, which makes 'the sell' much more difficult. In the last decade and a half, SOA has gone from being 'a difficult to sell value proposition' to 'one of the most popular items on CIO's wish list' for enterprises big and small. Rapid growth in acceptance of SOA has helped businesses and end users alike-it has positively impacted the top line of business houses and has given unforeseen agility to the EA landscape. This rapid growth in popularity for SOA also provided the fuel to fierce competition between the technology giants of the world, and enabled the rise of multiple open source vendors in space...
New Service Technology Resource Sites:
WhatIsCloud.com • WhatIsREST.com • ServiceOrientation.com
Arcitura Education has published advance and exclusive content on three new resource sites dedicated to Cloud Computing, Service-Orientation and REST. These sites are for open public usage and are also used as educational resource for select courses from the Cloud Certified Professional (CCP) and SOA Certified Professional (SOACP) programs. Specifically, WhatIsCloud.com provides advance content from the CCP Cloud Computing: Concepts & Technology supplement, which is forming the basis of the upcoming book by the same title as part of the Prentice Hall Service Technology Series. WhatIsREST.com offers content from the title "SOA with REST: Principles, Patterns and Constraints for Building Enterprise Solutions with REST", which was released earlier this year and officially launched at last month's 5th International SOA, Cloud + Service Technology Symposium in London. Finally, the new ServiceOrientation.com Website provides a master hub for new and existing content from various bodies of SOA-related resources that were previously published across different sites.