-thoughts on service orientated architectures
|
|
| Web Services -thoughts on service orientated architectures |
|
|
Sunday, March 02, 2003 Inter-operability or integration I came across a quote from Gartner "Interoperability is cheaper than integration", while preparing a presentation on Service Orientated Architecture. I also noted a piece by Sam Ruby entitled Evolution of the Weblog APIs where he states in his conclusion "If you are in the fortunate position where you essentially control both ends of the wire, and the parameters being passed are a simple series of strings and integers, use whatever seems easiest to you. This includes XML RPC, RMI, DCOM, or simply putting query arguments on the URL itself. I see these as illuminating an area where, to create truly loosely coupled systems, there needs to be much more focus. It is not about creating a better way to do integration rather it is about a better way to interoperate through loose coupling. If we must always worry about what flavor of API partners have we will be doomed to wander forever to find this particular "Holy Grail". On the other end of the spectrum there should not be afree for all. The reason we all subscribe to standards is not that we belive there will be only one, but rather they reduce the chaos down to a manageable set. The objective should be to get the semantics of what needs to be communicated close to right and then let the implementation of the end points take care of themselves and provide interoperability through loose coupling. If this was a mechanical system we were describing there would be an universal joint or a gearing system somewhere in the diagram. We are missing the set of universal services needed to implement the interoperability model. Just like we have a set of universal services for the consumer web we need them for the business web. I will confess to having a more than passing interest in this as I am part of Grand Central Communications and this is part of what we deliver. We should not mistake the pressures to interoperate for the pressure to integrate. It might be harder initially to design and implement interoperable interfaces but in the long run the loosely coupled results will allow more sustainable systems to be built. Comments [] posted by John McDowall | 3:32 PM |
|
|
|
|
|||||||||
|
 |
||||||||||||
|
|||||||||||||
