Traditionally when an application or service must transform data from one format to another in order to achieve some desired data integration goal, the most common and straightforward approach is to embed data transformation logic directly within the application. This approach makes introduction of transformation changes complex and limits scalability. The impact of the changes can spread throughout an implementation. This perspective is highly skewed to developer convenience at the expense of deployment flexibility and interoperability, and results in limited service reuse and increased data integration expense.
This discussion will show how embedding data transformation within the service runtime can address the challenges of reusability and scalability while enabling effective data and semantic integration. This makes it possible to handle data transformation declaratively, increasing the flexibility of the transformations.