Starting from when I was running IBM's MQSeries business, in the 1990s, I learnt a big lesson about seeing things from the user point of view. We had a great messaging product, and it started the EAI (Enterprise Application Integration) market rolling.
Soon, vendors were pitching the wonders of business integration through an all-encompassing EAI framework....and users started moaning about it being complicated and too hard.
Vendors brushed off these concerns and just shouted louder, and I was an evangelist in this....and then I started actually listening to users.
I remember pitching for all I was worth on the strategic value of EAI, and then a user saying to me, "Steve, we believe you. But we can't get there in one jump - at the moment, what we really need is to hook this application up with that one, that's all".
For a moment my strategic eye was offended. How could you take this wonderful, clever, strategic software and then just hook two applications together?
What a waste! But of course, I then learnt the practicalities of life, and the imperative to focus on the business need.
If the business needs Application A to talk to Application B, then that is what it will fund, and that is what it wants to achieve. Sweeping frameworks are all very well, but for most companies practical considerations come first.
Now I am having deja vu, all over again. I believe in SOA - I am an evangelist. I can see the huge benefits it promises as a strategic platform for business agility, business visibility and cost-efficiency.
And yet, talking to users it has finally sunk in that while some of the more lucky companies have the funding and resources to go the whole hog with SOA, there are a large number of users who 'just want to link A to B', but want to do so in a way that is consistent with a goal of enterprise-wide SOA some time in the future.
The new Lustratus report, free from the Lustratus web store, discusses a more tactical approach to SOA - "message-driven SOA". It points out that even for those companies who are terrified by the prospect of having to work out their process implementations and flows, change the way they work and deal with business transformation issues, there is a way to leverage SOA ideas in a tactical, simple way that is at least a step on the road to overall SOA adoption.
Message-driven SOA is almost a reprise of the tactical use of messaging in the 1990s, but with an SOA spin on it. So, message-based flows loosely couple applications and programs together, delivering the benefits of business integration without necessarily having to get tangled up in full-scale process re-engineering and modelling.
And yet, the reuse concept of SOA is also leveraged, together with the ability to expose these message-based integrations as SOA services.
Message-driven SOA may not be the answer to every problem. As a rule of thumb, it will be most attractive for integrations that are primarily of the application-to-application kind, where human interaction is limited and tasks are of short duration.
But it is well worth a look to see if this simpler approach to getting tactical SOA benefits might be useful