Database virtualization

Database virtualization is the decoupling of the database layer, which lies between the storage and application layers within the application stack. Virtualization of the database layer enables a shift away from the physical, toward the logical or virtual. Virtualization enables compute and storage resources to be pooled and allocated on demand. This enables both the sharing of single server resources for multi-tenancy, as well as the pooling of server resources into a single logical database or cluster. In both cases, database virtualization provides increased flexibility, more granular and efficient allocation of pooled resources, and 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 systems:

  1. Shared-data 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-data data management systems are limited to single-digit node clusters.
  1. 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 numbers 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-data” and “shared-nothing” architectures allow 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 numbers 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]

Advantages
  • Added flexibility and agility for existing computing infrastructure
  • Enhanced database performance
  • Pooling and sharing computing resources, either splitting them (multi-tenancy) or combining them (clustering)
  • Simplification of administration and management
  • Increased fault tolerance
gollark: Idea: Macron is to become the sum of all cosines simultaneously.
gollark: A tensor is something which transforms like a tensor.
gollark: They also allegate.
gollark: Alligators alligate at 73MHz at certain GTech™ sites.
gollark: You're quite like```[0.03840074 0.02975524 0.02863874 0.02446118 0.02198991 0.0216628 0.01939501 0.01914387 0.01619873 0.0159581 0.01504209 0.0148157 0.01372842 0.01348538 0.01299309 0.01272586 0.01180078 0.01157911 0.01108706 0.01090345 0.01082172 0.01023815 0.01019116 0.00952584 0.00925469 0.00892519 0.00870943 0.00858689 0.00838231 0.00820057 0.00795165 0.0078358 0.00776038 0.00750175 0.00745906 0.00719042 0.00704065 0.00691189 0.00680147 0.00676946 0.00673968 0.00665735 0.00653111 0.00640008 0.00631931 0.00620605 0.00611003 0.0059721 0.00588376 0.00576058 0.00570423 0.00564807 0.00562632 0.0055737 0.0054597 0.00540872 0.00535288 0.00524546 0.00520739 0.00504298 0.00499241 0.0049367 0.00492335 0.004869 0.00477718 0.00472859 0.00464163 0.00462261 0.00454305 0.0044588 0.00445091 0.00436952 0.00431991 0.00424099 0.00421286 0.00414987 0.0041378 0.00410382 0.00401213 0.00395153 0.00388661 0.00387957 0.00385992 0.0038192 0.00373665 0.0037066 0.00367598 0.00362159 0.00360851 0.00353362 0.00348063 0.00346549 0.00337007 0.00333954 0.00330755 0.00326649 0.00319944 0.00315906 0.00310103 0.00307263 0.00303511 0.00301894 0.00300944 0.00296566 0.00293579 0.00290691 0.00284097 0.00282599 0.00280492 0.00278099 0.00269841 0.00265956 0.00261216 0.00258167 0.00256163 0.00252229 0.00248712 0.00243954 0.00236763 0.00233683 0.002314 0.00230179 0.00226548 0.00224578 0.00220935 0.00216469 0.00215114 0.00214052 0.00207293 0.00204525 0.00202677 0.00199634]```

See also

References
  1. Clearly Defining Data Virtualization, Data Federation, and Data Integration


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.