Why an ESB is no longer suitable for data integration
In the past, integrations between applications were carried out using an enterprise service bus (ESB). But only large enterprises, with complex internal systems, technical skills and the budget, could implement an ESB.
Organizations today need an integration solution that can handle both real-time and batch integration needs, that has been built for cloud and mobile usage as well as on-premise, and that can work with a variety of communication formats and protocols. They need a better data transfer engine – an integration platform-as-a-service (iPaaS).
Related Article: Is it time to replace your old ESB?
Middleware technologies conceptualized in the 1990s were designed for stable, batch-oriented applications that ran behind a firewall, communicating only via XML and SOAP. The need now is for an integration solution that can handle both real-time and batch integration needs. Read more