Skip to main content

core-cdc (CDC a.k.a Change Data Capture)

It provides the core mechanism and required resources to implement “Change Data Capture” services…


PyPI Downloads Python Versions License Pipeline Status Docs Status Security

Installation

Install from PyPI using pip:

pip install core-cdc
uv pip install core-cdc  # Or using UV...

Features

Multi-Database CDC Support
  • MySQL Binary Log (BinLog) based change capture

  • MongoDB Change Streams for real-time event streaming

  • Extensible processor architecture for additional database engines

Comprehensive Event Handling
  • DML operations: INSERT, UPDATE, DELETE

  • DDL operations: CREATE, ALTER, DROP (schemas and tables), delivered to the targets as engine independent DdlEvent objects

  • Configurable event filtering by operation type

Flexible Target Replication
  • Implement your own target by subclassing ITarget

  • Send records to any destination: database, queue, data warehouse, etc.

  • Support for multiple simultaneous targets

Standardized Data Format
  • Common Record (data) and DdlEvent (schema changes) structures for cross-service integration

  • Includes metadata: timestamps, transaction IDs, source position

  • JSON serialization support for streaming and messaging systems

Production-Ready Features
  • Error handling: a failing event or target is logged without stopping the stream

  • Comprehensive logging for monitoring and debugging

  • Optional event timestamp column for UPSERT/MERGE operations

Quick Start

Installation

Install the package:

pip install core-cdc
uv pip install core-cdc     # Or using UV...
pip install -e ".[dev]"     # For development...

Setting Up Environment

  1. Install required libraries:

pip install --upgrade pip
pip install virtualenv
  1. Create Python virtual environment:

virtualenv --python=python3.12 .venv
  1. Activate the virtual environment:

source .venv/bin/activate

Install packages

pip install .
pip install -e ".[dev]"

Optional libraries

pip install '.[all]'    # MySQL + MongoDB
pip install '.[mysql]'  # MySQL BinLog support
pip install '.[mongo]'  # MongoDB Change Streams support

Check tests and coverage

python manager.py run-tests                   # unit tests
python manager.py run-tests --test-type integration
python manager.py run-coverage

The documentation is built with Sphinx, the docs extra has what it needs:

pip install -e ".[all,docs]"
cd docs && make clean && make html

Functional Tests

Functional tests require live database servers and are not discovered by pytest or tox automatically (files are named check_*.py to prevent accidental execution).

The helper script tests/functional/quick_test.sh checks connectivity, runs both MySQL and MongoDB test suites, and prints a metrics summary. They also check DDL events, transaction control queries, the JSON serialization of every type of column, the MongoDB invalidate events, the resume token and transactions (the tests of the column types change binlog_row_metadata in the server and restore it):

bash tests/functional/quick_test.sh

All connection parameters default to the Docker values below and can be overridden via environment variables (MYSQL_HOST, MYSQL_PASSWORD, MONGO_HOST, MONGO_DATABASE, etc.).

To run individual test files:

python manager.py run-tests --test-type functional --pattern "*.py"

Spinning Up Local Servers with Docker

MongoDB Replica Set (required for Change Streams):

docker network create mongoCluster

docker run -d --rm -p 27017:27017 --name mongo1 --network mongoCluster \
    mongo:5 mongod --replSet myReplicaSet --bind_ip localhost,mongo1

docker run -d --rm -p 27018:27017 --name mongo2 --network mongoCluster \
    mongo:5 mongod --replSet myReplicaSet --bind_ip localhost,mongo2

docker run -d --rm -p 27019:27017 --name mongo3 --network mongoCluster \
    mongo:5 mongod --replSet myReplicaSet --bind_ip localhost,mongo3

docker exec -it mongo1 mongosh --eval "rs.initiate({
  _id: \"myReplicaSet\",
  members: [
    {_id: 0, host: \"mongo1\"},
    {_id: 1, host: \"mongo2\"},
    {_id: 2, host: \"mongo3\"}
  ]
})"

Check cluster status:

docker ps
docker exec -it mongo1 mongosh --eval "rs.status()"

MySQL (BinLog replication enabled by default in the official image):

docker run \
  --env=MYSQL_ROOT_PASSWORD=mysql_password \
  --volume=/var/lib/mysql \
  -p 3306:3306 \
  --restart=no \
  -d mysql:latest

Tested Versions

These are the versions the library was verified with. Live means the functional tests (tests/functional) ran against real servers; the unit and integration tests use mocks and do not need any server.

Component

Versions

How it was tested

MySQL

9.7.2, 8.4.11, 8.0.46, 5.7.44

Live (official Docker images, ROW format). GTIDs on and off (9.7, 8.4). binlog_row_metadata FULL and MINIMAL (9.7, 8.4, 8.0).

MongoDB

6.0.28, 5.0.31

Live (replica set, official mongo:6 and mongo:5 images): change streams, DDL, invalidate, resume tokens and transactions. In 6.0 also the expanded events (create, createIndexes, dropIndexes, modify) and wallTime.

Python

CPython 3.9, 3.10, 3.11, 3.12, 3.13, 3.14 and PyPy 3.11

tox: unit and integration tests, and the live functional tests (MySQL 8.4 and MongoDB 5), on each one.

Libraries

mysql-replication 1.0.15 and 1.0.17; pymongo 4.17.0 and 4.18.1; PyMySQL 1.1.3 and 1.2.3; core-mixins 3.2.0 and 3.2.2

Both sets of versions ran the live tests.

Minimum declared libraries

mysql-replication 1.0.9, pymongo 4.0.0, core-mixins 3.2.0

Unit and integration tests on Python 3.9 (not live).

Notes:

  • MySQL 5.7 must be started with the binary log enabled (--server-id=1 --log-bin=mysql-bin --binlog-format=ROW). Four of the six MySQL functional tests run there: the other two are about binlog_row_metadata, a variable that does not exist in 5.7 (its column types are read from the database, see the MySQL section).

  • MongoDB create, createIndexes, dropIndexes and modify events need MongoDB 6.0+ and showExpandedEvents; rename, drop, dropDatabase and invalidate are sent by 5.0 too. Only the sharding operations (shardCollection, refineCollectionShardKey, reshardCollection) were tested with simulated events, since they need a sharded cluster.

Not tested (they may work, there is no verification): MySQL 8.1 to 8.3 and the 9.x versions other than 9.7.2, MariaDB, Percona and managed services (Amazon RDS / Aurora, Cloud SQL, Atlas), MongoDB before 5.0 and 7.0 or later, other minor versions of the ones listed, and sharded MongoDB clusters.

Implemented CDC Engines

The following database engines have CDC implementations:

Fully Implemented

MySQL - Binary Log (BinLog) based CDC
  • Uses mysql-replication library

  • Captures INSERT, UPDATE, DELETE operations

  • Supports DDL events (CREATE, ALTER, DROP)

  • Fallback mechanism for column name resolution

  • See: core_cdc/processors/mysql/

MongoDB - Change Streams based CDC
  • Uses native MongoDB Change Streams

  • Captures INSERT, UPDATE, DELETE operations

  • Requires replica set configuration

  • Real-time event streaming

  • See: core_cdc/processors/mongo/

Planned / Documentation Only

MS SQL Server and Oracle implementations are not yet included. Reference guides and implementation templates are available in the documentation.

Contributing

Contributions are welcome! Please:

  1. Fork the repository

  2. Create a feature branch

  3. Write tests for new functionality

  4. Ensure all tests pass and coverage stays at 100 %: python manager.py run-coverage

  5. Run the linters and type checkers: ruff check core_cdc, ty check core_cdc, mypy --explicit-package-bases core_cdc, pyright core_cdc and pylint core_cdc

  6. Run the security checks: bandit -r core_cdc and pip-audit

  7. Submit a pull request

License

This project is licensed under the MIT License. See the LICENSE file for details.

Support

For questions or support, please open an issue on GitLab or contact the maintainers.

Authors

Release files for core-cdc 4.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for core-cdc 4.0.0
File Size Uploaded
core_cdc-4.0.0.tar.gz 29.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for core-cdc 4.0.0
File Interpreter ABI Platform
core_cdc-4.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 57.1 kB

Release files / core_cdc-4.0.0.tar.gz

Download URL core_cdc-4.0.0.tar.gz
Size 29.2 kB
Tags Source
SHA-256 checksum
How to use checksums
096e19ac0e9dcd3d43014a3b1b6f3d300ae24f672f64c4ac5a1b3e6e7318a957
BLAKE2b-256 checksum
How to use checksums
355406091ffe15f623905796452009e9dcd1803caa62a55429825c6b75bcb15b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Release files / core_cdc-4.0.0-py3-none-any.whl

Download URL core_cdc-4.0.0-py3-none-any.whl
Size 27.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
76259d7347687af5d83820d4f5b5a54539a17e8876ad51418f1ea4947b898618
BLAKE2b-256 checksum
How to use checksums
804f4bfeb8b41b976c7bd43f8a9739e6d52cd1789869ae2e97b4f8ddf08693c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Release history Release notifications | RSS feed

4.1.0

2 release files

This release

4.0.0 This release

2 release files

3.1.2

2 release files

3.1.1

2 release files

3.1.0

2 release files

3.0.1

2 release files

3.0.0

2 release files

2.0.2

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.5

2 release files

1.0.4

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page