Skip to content

DOC-6878 Expand RDI FAQ CDC section with all supported databases #3700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andy-stark-redis merged 2 commits into from
Jul 23, 2026
Merged

DOC-6878 Expand RDI FAQ CDC section with all supported databases #3700

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2b449b4
DOC-6878 Expand RDI FAQ CDC section with all supported databases
andy-stark-redis Jul 23, 2026
bf0d906
DOC-6878 Drop embedded supported-databases table from FAQ
andy-stark-redis Jul 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 21 additions & 8 deletions content/integrate/redis-data-integration/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,27 @@ Redis Enterprise shards (primary and replica) for the staging database.

## How does RDI track data changes in the source database?

RDI uses mechanisms that are specific for each of the supported
source databases:

- **Oracle**: RDI uses `logminer` to parse the Oracle `binary log` and `archive logs`. This
lists any changes in a database view that RDI can query.
- **MySQL/MariaDB**: RDI uses `binary log replication` to get all the commits.
- **PostgreSQL**: RDI uses the `pgoutput` plugin.
- **SQL Server**: RDI uses the CDC mechanism.
RDI uses change data capture (CDC) mechanisms that are specific to each of the
supported source databases:

- **Oracle**: RDI uses `LogMiner` to read Oracle's `redo logs` and `archive logs`,
or, alternatively, `XStream`.
- **MySQL/MariaDB**: RDI uses `binary log` (binlog) replication to capture all commits.
- **PostgreSQL**: RDI uses the `pgoutput` logical decoding plugin. The same
applies to the PostgreSQL-compatible databases that RDI supports, including
Supabase, AlloyDB for PostgreSQL, Amazon Aurora/RDS for PostgreSQL, and Neon.
- **SQL Server**: RDI uses the database's built-in CDC feature.
- **MongoDB**: RDI uses `change streams` to read the `oplog`. The source must be
a replica set, sharded cluster, or MongoDB Atlas deployment, because a
standalone MongoDB server has no oplog.
- **Google Cloud Spanner**: RDI uses `Spanner change streams` for the streaming
phase and the JDBC driver for the initial snapshot. Spanner is supported only
when RDI is deployed on Kubernetes with Helm.
- **Snowflake** (preview): RDI uses `Snowflake Streams`. Snowflake is supported
only when RDI is deployed on Kubernetes with Helm.

For the complete list of supported source databases and versions, see
[Prepare source databases]({{< relref "/integrate/redis-data-integration/data-pipelines/prepare-dbs" >}}).

## How much data can RDI process?

Expand Down
Loading