Discovering Data Services through Use Cases: Legacy Integration

January 26, 2012 --

Talend recently announced the availability of the Talend Platform for Data Services. Built around Talend v5’s data integration and ESB technologies, it lets IT organizations operationalize data through the single development, deployment, runtime and monitoring environment of the Talend Unified Platform.

Through a couple blog posts, we look at typical use cases of the Talend Platform for Data Services. In recent posts, we looked at data virtualization and guaranteed delivery. This post explains how Data Services facilitate integration of legacy applications.

One of the key aspects of integrating legacy systems is the ability to preserve the operation of existing applications while the transition occurs.

Even when organizations embrace a modern architecture, based on a Bus or Services architecture, it’s often hard to simply "service enable" running applications, which are often mission critical. In addition, it’s usually impossible to perform a big bang and to change everything at the same time.

An interesting use case would be the integration of legacy manufacturing systems, feeding metrics and operational data via messages to a Hub. Implementing Data Services in Hub mode allows these messages to be consumed centrally, enriched & transformed, and most importantly abstracted, such that other applications can now consume this data without being exposed to internal dependencies on such legacy systems.

Over time as the manufacturing software gets modernized, “intelligent” end-points start to be deployed that participate to a distributed Bus architecture and are able to transform & cleanse data at the source, adhering to a canonical message model and alleviating the need to perform this processing in the ESB Hub. At the same time, the remnants of the legacy architecture continue to function in Hub mode.

This model allows a smooth transition from a legacy Hub architecture to a service-enabled model, relying on a Bus architecture.