Jump to content

Database virtualization

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 99.70.2.221 (talk) at 16:20, 11 April 2012. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Database virtualization it is the decoupling of the database layer, which lies between the storage and application layers within the application stack. Virtualization at the database layer allows hardware resources to be extended to allow for better sharing resources between applications and users, masking of the physical location and configuration of a database from querying programs, as well as enable more scalable computing.

Virtual Data Partitioning

The act of partitioning data stores as a database grows has been in use for several decades. There are two primary ways that data has been partitioned inside legacy data management solutions:

I. Shared All Databases–an architecture that assumes all database cluster nodes share a single partition. Inter-node communications is used to synchronize update activities performed by different nodes on the cluster. Shared-all data management systems are limited to single-digit node clusters.

II. Shared-Nothing Databases–an architecture in which all data is segregated to internally managed partitions with clear, well-defined data location boundaries. Shared-nothing databases require manual partition management.

In virtual partitioning, logical data is abstracted from physical data by autonomously creating and managing large number of data partitions (100s to 1000s). Because they are autonomously maintained, resources required to manage the partitions are minimal. This kind of massive partitioning results in:

  • partitions that are small, efficiently managed and load balanced; and
  • systems that do not required re-partitioning events to define additional partitions , even when hardware is changed

“Shared-all” and “shared nothing” architectures allowing scalability through multiple data partitions and cross-partition querying and transaction processing without full partition scanning.

Horizontal Data Partitioning

Partitioning database sources from consumers is a fundamental concept. With greater number of database sources, inserting a horizontal data virtualization layer between the sources and consumers helps address this complexity. Rick van der Lans, author of multiple books on SQL and relational databases, has defined data virtualization as "the process of offering data consumers a data access interface that hides the technical aspects of stored data, such as location, storage structure, API, access language, and storage technology." [1]

Database Virtualization Advantages

  • Added flexibility and agility for existing computing infrastructure
  • Enhanced database performance
  • Pooling and sharing computing resources
  • Simplification of administration and management
  • Increased fault tolerance

See also

References