Data Services layer is an abstraction layer to provide data to multiple consumers and usually it is deployed at an enterprise-wide scale. Data Virtualization software has the ability to create easily new Data Services using the views previously created in the virtual layer.
In many projects it's necessary to have a common consistent and scalable data services infrastructure. Why? What are the most common issues?
Ok, but, what are the benefits of having a Data Services layer?
Let's suppose the following scenario for this tutorial:
People from another department have an application that connects to the company's CRM using an specific Web Service (developed only for this purpose) but now, they want to use the Data Virtualization infrastructure to get the unified customer data (to avoid connecting to the physical source systems). They have to migrate their application and the quick approach is to point to another Web Service with similar operations to the previous one but this new Service will have more output fields (it adds more information).
Summarizing, two actions have to be done:
In this example, the contract will be the WSDL of a Web Service without implementation in Denodo. In the next section you will learn how to create a new type of element (interface element) very useful in this kind of projects.
With these points in mind, in this tutorial we will use Denodo to learn how to: