-
Notifications
You must be signed in to change notification settings - Fork 445
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6fa9d5c
commit 495b8d9
Showing
1 changed file
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Module 2: Change Data Capture: Enabling Event-Driven Architectures | ||
|
||
|
||
## Introduction | ||
Change Data Capture, commonly known as CDC, is an efficient way to track changes in a database. | ||
|
||
The purpose of CDC is to capture insertions, updates, and deletions applied to a database and to make this change data available in a format easily consumable by downstream applications. | ||
Why do we need CDC pattern? | ||
|
||
Real-time Data Syncing: CDC facilitates near-real-time data integration and syncing. | ||
Efficient Data Pipelines: It allows incremental data loading, which is more efficient than bulk load operations. | ||
Minimized System Impact: CDC minimizes the impact on the source system by reducing the need for performance-intensive queries. | ||
Event-Driven Architectures: It enables event-driven architectures by streaming database events. |