There's a large gaping hole in the capabilities enterprise application integration (EAI) – and its successor, enterprise service buses – can deliver. Current middleware strategies fall short in addressing data integration and data quality issues – and this is costing organizations.
These are points raised by Dave Linthicum and Ash Parikh in a recent Webinar, I had the opportunity to moderate, posted over at the ebizQ site. Dave, who literally wrote the book on “Enterprise Application Integration” back in the 1990s, says EAI and ESB approaches are not suited for today's high-transaction data integration needs, and have great limitations. But still, many organizations persist in attempting to plug in these types of solutions into vexing business problems that require a more holistic architectural approach. “There are a lot of people trying to put square pegs into round holes,” he says.
Dave says that while the square-peg-in-a-round-hole approach will work for a while, it's far more costly in the long run. “With EAI and ESB technology, there are certain instances and problem domains where they're a fit,” he explains. “But you need to understand there are certain limitations that are part of that technology that should be considered. Ultimately, if you don't consider them and pick those technology approaches anyway, you're going to start running into walls that are very difficult to back up and get around as you move the architecture forward.”
I posted a summary of points raised in the Webinar here at the Perspectives site.