Section 10.2: Replication & Virtualization

DAMA Certified Data Management Professional CDMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & DMBoK Framework

1.1 CDMP Exam Details & Strategy 1.2 The DMBoK Framework 1.3 Data Management Organization & Roles

2 Chapter 2: Data Governance (Part A)

2.1 Data Governance Principles & Drivers 2.2 Operating Models & Structures 2.3 Policies, Standards, and Procedures

3 Chapter 2: Data Governance (Part B)

2.4 Data Stewardship 2.5 Governance Metrics & Implementation

4 Chapter 3: Data Modeling and Design (Part A)

Section 3.1: Conceptual, Logical, and Physical Models Section 3.2: ERD Notations & Relational Modeling Section 3.3: Normalization

5 Chapter 3: Data Modeling and Design (Part B)

3.4 Dimensional Modeling 3.5 Naming Standards & Modeling Best Practices

6 Chapter 4: Data Quality (Part A)

Section 4.1: Data Quality Dimensions Section 4.2: Data Quality Policy & Rules Section 4.3: DMAIC & DQ Improvement Lifecycle

7 Chapter 4: Data Quality (Part B)

4.4 Root-Cause Analysis & Remediation 4.5 DQ Metrics, Tools, and Reporting

8 Chapter 5: Metadata Management (Part A)

5.1 Business, Technical, and Operational Metadata 5.2 Metadata Lineage & Impact Analysis 5.3 Repository Architectures

9 Chapter 5: Metadata Management (Part B)

5.4 Standards and Semantics 5.5 Metadata Governance & Integration

10 Chapter 6: Master and Reference Data Management

6.1 Master vs Reference Data 6.2 MDM Repository Architectures 6.3 Match-Merge & Identity Resolution 6.4 Reference Data Governance & Standards

11 Chapter 7: Data Warehousing and Business Intelligence

7.1 DW Architectures: Inmon vs Kimball 7.2 Data Warehousing Storage & Load Patterns 7.3 BI Delivery & OLAP 7.4 Data Marts & Enterprise Data Warehouses

12 Chapter 8: Data Architecture

8.1 Enterprise Data Architecture & Zachman Framework 8.2 Data Flow Diagrams & Value Chains 8.3 Architecture Frameworks & Standards

13 Chapter 9: Document and Content Management

9.1 Records Management & ECM 9.2 Retention, Disposal, and E-Discovery 9.3 ARMA GARP Principles & Taxonomies

14 Chapter 10: Data Integration and Interoperability

Section 10.1: Integration Patterns & Technologies Section 10.2: Replication & Virtualization Section 10.3: Canonical Models & Integration Standards

15 Chapter 11: Data Security

Section 11.1: Security Principles: CIA Triad & Privacy Section 11.2: Access Control & Encryption Section 11.3: Security Regulations & Standards

16 Chapter 12: Data Storage and Operations

Section 12.1: Database Technologies & DBA Roles Section 12.2: Backup, Recovery, and High Availability Section 12.3: Performance Tuning & Operations

17 Chapter 13: Big Data and Data Science

13.1 Big Data V's & Technologies

18 Chapter 14: Data Ethics

14.1 DMBoK Data Ethics Framework

19 Chapter 15: Data Management Process and Maturity

15.1 Maturity Assessment Frameworks

Section 10.2: Replication & Virtualization

Key Takeaways Explain This Topic AI

Data replication models range from synchronous (immediate consistency, higher write latency) to asynchronous (eventual consistency, lower latency, risk of data loss).

Data virtualization provides a unified, logical view of data across disparate sources in real time without physically moving or copying the data, reducing storage costs and consolidation times.

Query federation engines in virtualization architectures compile, optimize, and distribute queries to underlying source systems, but they can create performance bottlenecks on operational databases.

API-based, service-oriented integration patterns (REST, SOAP) provide encapsulation and abstraction layers that shield consumers from underlying physical schemas and data stores.

Last updated: July 2026

Data Replication Models

Data replication is the process of copying and maintaining data objects (such as tables or database schemas) across multiple database nodes or geographic sites. Replication is primarily used to ensure high availability, support disaster recovery, enable load balancing, and improve data access speed for localized users.

Synchronous Replication : In a synchronous write operation, a transaction is committed on the primary node and all replica nodes before a final confirmation is returned to the client application. This guarantees a Recovery Point Objective (RPO) of zero, meaning no data loss can occur during a sudden failover, and maintains strict consistency across all database nodes. The significant trade-off is latency: write performance is limited by the slowest network link and the response time of the furthest replica. Furthermore, if a replica node becomes unavailable, subsequent writes can be blocked.

Asynchronous Replication : Under asynchronous replication, the primary node commits the write transaction immediately and notifies the client. The update is then transmitted to the replica nodes with a delay, known as replication lag . This model provides high transactional throughput and minimal write latency, making it suitable for geographical backups. The major risk is data loss: if the primary system fails before the replica has received the latest updates, some transactional data will be permanently lost, resulting in a non-zero RPO and eventual consistency across nodes.

Active-Passive vs. Active-Active Topologies : In an active-passive configuration, writes are processed by a single primary node and replicated to secondary standby nodes that remain read-only or idle. In an active-active configuration, writes can be executed on multiple nodes concurrently. This requires complex conflict resolution policies, such as Last-Write-Wins (LWW) (based on system timestamps), vector clocks, or customized business logic to reconcile updates to the same record from different nodes.

In active-active topologies, conflict resolution is one of the most significant engineering challenges. When two nodes accept updates to the same row simultaneously, the system must reconcile the differences. The simplest method is LWW, which uses physical database timestamps to determine the final state. However, clock drift across servers can lead to incorrect data sequencing. To overcome this, distributed systems employ logical clocks, such as vector clocks , or establish application-level reconciliation rules (e.g., merging shopping cart items or routing conflicting writes to a human-review queue). These strategies ensure consistency but increase transactional complexity and development overhead.

Data Virtualization: Principles and Architecture

Data virtualization is an integration pattern that creates a logical data access layer. It presents a unified, single view of data from heterogeneous, physically separated sources to applications and end users without physically moving, copying, or duplicating the data into a central store.

At the core of data virtualization is query federation . When a user executes a query against a virtual view, the virtualization engine performs several steps:

Parsing and Optimization : It analyzes the logical query and identifies the physical locations of the required data elements.

Push-Down Queries : It translates the query into sub-queries optimized for the native languages of the source systems (e.g., SQL for relational databases, API calls for web services, or custom filters for flat files) and sends them to the respective sources for execution.

Aggregation and Formatting : It gathers the partial results returned by the sources, executes any necessary joins, sorting, or format transformations in its cache or memory, and delivers the consolidated output to the user.

To mitigate query latency, modern data virtualization engines implement sophisticated optimization strategies. The most common is metadata caching , where the engine caches the schemas and statistical profiles of the source systems, rather than the data itself, to construct optimal execution plans. Furthermore, the engine may perform hybrid query processing , which involves temporary staging of small datasets from one source on the virtualization server to perform high-speed in-memory joins with a larger dataset from another source. Despite these optimizations, architects must establish strict query timeouts and resource governance policies to prevent federated queries from exhausting database connections on critical source systems.

Benefits and Drawbacks of Data Virtualization

Feature Benefits Drawbacks & Challenges

Storage Overhead Zero physical copying saves substantial storage costs. High network traffic and bandwidth consumption during query execution.

Latency & Timing Real-time access to operational data (no batch delay). Query performance is restricted by network speeds and source response times.

Development Time Rapid prototyping; new virtual views can be deployed in minutes. Lack of historical depth; cannot track historical changes if source data is overwritten.

Security & Governance Centralized security policies can be enforced at the virtual layer. Operational risk; federated queries can overload active transactional databases.

API-Based and Service-Oriented Integration

Modern data integration increasingly relies on Application Programming Interfaces (APIs) and Service-Oriented Architecture (SOA) to expose data as reusable services rather than direct database accesses.

SOAP (Simple Object Access Protocol) : SOAP is a highly structured, XML-based messaging protocol. It relies on strict contracts defined via Web Services Description Language (WSDL) . SOAP has built-in standards for security ( WS-Security ) and transactional compliance ( WS-AtomicTransaction ), making it popular for legacy enterprise applications. However, its verbose XML structure creates significant network and processing overhead.

REST (Representational State Transfer) : REST is an architectural style that relies on standard HTTP methods (GET, POST, PUT, DELETE) and operates on resources represented by URIs. REST is stateless and typically uses lightweight payloads like JSON (JavaScript Object Notation). It is highly scalable, simple to implement, and represents the industry standard for modern web and mobile applications.

While REST is highly optimized for performance and ease of use, SOAP remains essential in compliance-heavy industries. SOAP's support for WS-Security allows message-level encryption and digital signatures, ensuring that the data payload remains secure even as it passes through untrusted intermediary servers. Additionally, SOAP's support for WS-ReliableMessaging guarantees delivery, which is vital for financial applications where message loss cannot be tolerated. In contrast, REST relies on transport-layer security (HTTPS) and application-level retry mechanisms. When adopting a microservices architecture, organizations must weigh these security and transactional integrity guarantees against the agility and speed of REST APIs.

Service-oriented integration provides encapsulation . By accessing data through APIs, the underlying database schema is shielded from client applications. A database administrator can alter table structures or migrate from a relational database to a NoSQL store without breaking consuming systems, provided the API payload contract is maintained.