Generally, when I read something about service-oriented architecture and integration, it's focused on how SOA can address integration. There's some debate over how much your SOA efforts should focus on integration -- it's an easy selling point, and possibly a good way to achieve an ROI, but many SOA experts say you can short-change yourself by focusing too much on integration.
That's old hat, right? But this month, I ran across a different kind of white paper about SOA and integration. The piece was published by BP Trends and written by Dr. Gopala Krishna Behara, a senior enterprise architect for Wipro Consulting Services.
I'll be honest with you -- I debated whether to refer to this white paper. Frankly, I found it a bit hard to follow and sometimes I felt the author lost focus from his main point. But I decided to point it out to you for a few reasons:
- If you're new to integration -- say, if you're a business manager -- he gives a fantastic breakdown of the types of integration and integration technologies. I would have loved to have this piece when I first started writing about integration, because he's done an excellent job of identifying the categories of integration you'll encounter in an enterprise.
- It explains the evolution of integration. Under the "Service Oriented Integration" section, Behara walks you through the evolution of integration from a very concrete, point-to-point process to a more high-level, abstract process that involves integrating services and business functions. I think this section works well alone to explain service integration, but it also helps you understand things such as how metadata can be used for integration.
- It takes the rather unusual position of looking at how integration techniques and technologies can help you with SOA. As I mentioned, almost all the pieces I've seen look at the reverse, how SOA can help with integration, so it's refreshing and very illuminating to see how, for instance, the technologies you've used for integration can be used in a SOA.
One of the topics he covers briefly is semantic integration, which is something I've been researching lately. Semantic integration isn't a huge topic right now -- in fact, it's still very much the domain of large companies. But I suspect you'll be hearing more about it in the coming years as vendors acquire semantic companies and start to incorporate those functions into their products.
Recently I interviewed Vickie Farrell, Neoview Product Management, of Hewlett-Packard's Business Information Optimization, about semantic integration. Farrell explained how semantic technologies can help with integration and offered some real-world applications, adding that most CIOs will encounter semantic integration technologies through other products:
We are starting to see more and more large mainstream companies acquire the technology and bake it into their products. That's probably how most people will see it, is baked it into those products.https://o1.qnsr.com/log/p.gif?;n=203;c=204663295;s=11915;x=7936;f=201904081034270;u=j;z=TIMESTAMP;a=20410779;e=i
Behara's paper managed to help me fill in a few gaps about metadata and integration, which in turn helped me understand semantic integration a bit better.
Of course, providing a history of integration was not Behara's goal in the "SOA and Integration" white paper. According to the conclusion, he was attempting to show how integration technologies can be leveraged for SOA.
As I said, I found that thesis a bit hard to follow, but enterprise architects probably will find it much clearer. For the more casual integration reader, however, Behara has managed to write a useful resource that might address those nagging integration questions you couldn't find answered anywhere else.