I was amused by Steve’s blog item on why Integration didn’t seem to be cool (partly because I can’t honestly remember when it was cool).
When vendors discuss new ways of rebadging integration as something else I am reminded of the scene from Spinal Tap when Nigel Tufnel explains hat his amps are louder because they are labeled from 1 to 11 “Well, it’s one louder, isn’t it? It’s not ten.” Or to put it into the integration context: “It more agile isn’t it? It’s not slow to change “
To be fair the attraction of going for the new and cool terminology is understandable: Any explanation of an integration strategy can feel a bit like making a list of New Years resolutions. It tends to highlight all the bad habits you have (your mainframe can’t communicate with the Sun servers you bought 10 years ago etc) and may not put you in a good light. Worse still putting it all into a business plan to give to your CEO/CIO is like announcing your list of New Years resolutions to your spouse: He/she has probably heard all these resolutions last year and the year before that and noticed that you are not yet running 20 miles a day or spending quality time with the family goldfish.
So when your friend down the pub (the software vendor) explains that by buying these new running shoes you will be able to run further and keep track of the distance run, it is obviously tempting – analogies to business intelligence are purely intentional. We will have to wait and see if the CEO/CIO is any more convinced that the spouse!