|
Launch Your Legacy Code Using an Enterprise Service Bus |
|
According to Sirius Solutions Architect Michael T. Prinster, there’s a lot of confusion about what an Enterprise Service Bus (ESB) actually is, and how the implementation of ESB can simplify the addition or migration of enterprise applications.
Although many software products have claimed to be one sort of “bus” or another over the years, the Enterprise Service Bus as an architectural pattern has gained a lot of traction with the rising popularity of service-oriented architecture (SOA).
In large part, this is because the Web services commonly leveraged as the “service” part of SOA provide a simple, standardized mechanism which allows a lot of enterprise assets to “get on the bus” and talk to each other using common protocols such as SOAP over HTTP. (Some “buses” have dwindled in popularity precisely because the effort to get enterprise assets converted to use their less-popular protocols, transports or approaches was simply too complex an undertaking. CORBA, anyone?)
Today’s IBM ESB products can do a lot more than just connect two willing Web services, however, and this is where the story starts getting good for clients with legacy code assets.
IBM enterprise service bus products can:
- Cut through the tangled knot of interconnections between clients’ legacy data and applications,
- Provide new and often better ways for clients to connect with their customers and suppliers, and
- Allow clients to modernize legacy code assets at their own pace.
Mike Prinster has written an article that focuses on the first of these benefits: simplifying the interconnections between legacy data and applications.
» Download the complete article
|
