Development of SOA Thought Leadership.
- Mark Skilton
- May 23, 2007
- 2 min read
May 23 2007 Development of SOA Thought Leadership.
Services as the glue between federated domains
In a recent meeting with Miko Matsumura Vice president of WebMethods SOA solutions we discussed the approach to service orientation and how the paradigm was evolving towards a lifecycle governance process. Miko regarded the Services definition as explicit conversations (sharing data and conversation) and implicit conversations – powerflows between portfolios which a distributed system. The key challenge is the managing of federated policies in SOA. This is a key principle observed in the OASIS model which describes SOA as the exchange of services between different domains through definitions of public and private domain views as encapsulated services.
Rewriting Metcalf’s law with SOA
In discussion with Miko he theorised that SOA is another supporter of Moore’s Law of increasing processing power with reduced cost through services. SOA is also supporting Gilder’s Law in that bandwidth would drive increasing uptake of services via network capabilities. This leads me to think about Metcalf’s law and the paradigm of SOA as seeking to reduce the number of logical nodes through service orientation. It seems that unlike the other laws, SOA is rewriting this law to say that the increase in value is inversely to some power proportionally to the number of nodes in the system.
The state of interoperability standards
In discussion with Miko on interoperability standards we saw that this would occur on at least two levels: frameworks to define separation of architectural concerns and specific standards to define the relationships of concerns. The former could be seen in the development of OASIS SOA reference model and in particular its general definitions. The definition of relationships between architecture for services interoperability was more specific around encoding standards. Currently UDDI, ebXML, .NET services, WS*Policy was still a very small intersection and reflected the current situation for more development required to get stronger encapsulation connections between standards.
Comments