Japan
Germany
Show-Stopper Problems with Integration Brokers
How limited support Event-Driven Architecture (EDA) restricts the value of Integration Broker Technology.
Executive Summary
Most real-world integration scenarios in a typical enterprise involve multiple applications (or application components) that run on distinct physical machines across the enterprise network, are developed in different languages and run on different operating systems. As such, the typical scenario for integration involves the flow of events ( EDA ) and exchanges of requests ( SOA ) between business components distributed across a heterogeneous network.
A Forrester survey estimates that 64 percent of companies spend between 60 and 80 percent of their integration budget on consulting services, most of which go towards programming the infrastructure to connect and transfer events through the enterprise. The reason for these continued high costs lies in the fact that in real-world implementation conditions, current integration solutions suffer from some critical problems in the handling of request/reply interactions (SOA) and event-flows (EDA) resulting in rigid, complex implementations that are difficult to maintain and modify, leading to delayed projects, poor ROI and major cost overruns.
This whitepaper analyses some critical implementation-level problems faced by current integration broker technology in real-world implementations. Most of these problems occur because existing integration products do not seamlessly support SOA and EDA within a single framework - a shortcoming that is addressed by modern ESB implementations via SCA (Service Component Architecture).
