Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Miko Matsumura on Oct 12, 2006 04:46 PM
According to the SOA Reference Model document itself, a reference model is an abstract framework for understanding significant relationships among the entities of some environment. It enables the development of specific reference or concrete architectures using consistent standards or specifications supporting that environment. A reference model consists of a minimal set of unifying concepts, axioms and relationships within a particular problem domain, and is independent of specific standards, technologies, implementations, or other concrete details.
The reference model defines SOA as:
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
Now SOA has a standardized reference model, thanks to the work of OASIS SOA-RM technical committee. According to an email sent to the OASIS Reference Model Technical Committee, Duane Nickull, chair of the TC notified the group's status on the standardization vote as follows:
The Ballot to advance the Reference Model for SOA to become a full OASIS Standard received 89 positive votes, the second highest number of positive votes anyone on the TC can recall being cast to support a standard. The single no vote came from Avaya Inc. The sole statement provided by a representative from that company was:
"Too vague and confusing, e.g. things which are not SOA can be mapped into this and claim they conform to this SOA model."
Despite this sole dissenting vote, the techical committee, after approaching Avaya with a formal letter and expressing an interest to resolve any issues with the spec, the Technical Committee decided to move ahead according to the OASIS rules and move to a standard with a final tally of 89 organizations supporting, one against.
The Reference Model can be downloaded here:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
The Agile Business Analyst: Skills and Techniques needed for Agile
Free $40 SOA Demystified Book Offer
Usage Landscape: Enterprise Open Source Data Integration
Comprehensive Threat Protection for REST, SOA, and Web 2.0 Applications
Would you enroll in an India Forex Group i.e http://www.indiaforex.com Groups?
Those Avaya guys, they're smart. I honestly don't know what value, exactly, the RM provides ...
Also notice noone from Microsoft, IBM or Oracle on the membership list. This lack of major vendor leadership or support always concerned me.
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
I find this definition surprising as I've never heard SOA described in this manner anywhere else. No mention of loose coupling, no mention of standard protocols, etc. I'm curious why this definition is the way it is.
It is so loosely defined that everything from CORBA to EAI and grid systems fit into this definition.Secondly, do the component services have to be distributed by definition? It should be easier to distribute the capabilities of a choreographed business process or a business service which follows the SOA principles. Any comments on that?
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
4 comments
Watch Thread Reply