What is a data abstraction layer?

Use data abstraction to hide complexity and simplify information access

A data abstraction layer bridges the gap between business needs and source data’s original form. This best practice implementation of data virtualization provides the following benefits:

  • Simplify information access – Bridge business and IT terminology and technology so both can succeed.
  • Common business view of the data – Gain agility, efficiency and reuse across applications via an enterprise information model or “Canonical” model.
  • More accurate data – Consistently apply data quality and validation rules across all data sources.
  • More secure data – Consistently apply data security rules across all data sources and consumers via a unified security framework.
  • End-to-end control – Use a data virtualization platform to consistently manage data access and delivery across multiple sources and consumers.
  • Business and IT change insulation – Insulate consuming applications from changes in the source and vice versa. Business users and applications developers work with a more stable view of the data. IT can make ongoing changes and relocation of physical data sources without impacting information users.

TIBCO's data abstraction reference architecture

Data abstraction using TIBCO data virtualization

  • Application layer – The “Application Layer” serves to map the Business Layer into the format which each Data Consumer (user or application) wants to consume the data.  It might mean formatting into XML for Web services or creating views with different alias names that match the way the consumers are used to seeing their data.
  • Business layer – The “Business Layer” is predicated on the idea that the business has a standard or canonical way to describing key business entities such as customers and products.  In the financial industry, one often accesses information according to financial instruments and issuers amongst many other entities. Typically, a data modeler would work with business experts and data providers to define a set of “logical” or “canonical” views that represent these business entities. These views are reusable components that can and should be used multiple consumers via the Application Layer.
  • Physical layer – In the “Physical Layer,” data Sources are integrated into the abstraction.  Value added tasks such as name aliasing, value formatting, data type casting, derived columns and light data quality checks are also defined here. Metadata used here is typically derived from the physical sources.
data abstraction diagram