Skip to content
Open
Changes from all commits
Commits
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
8 changes: 7 additions & 1 deletion integration-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,10 @@ You can use TiCDC to replicate incremental data from TiDB to Confluent Cloud, an

## Integrate with Apache Kafka and Apache Flink

You can use TiCDC to replicate incremental data from TiDB to Apache Kafka, and consume the data using Apache Flink. For details, see [Integrate with Apache Kafka and Apache Flink](/replicate-data-to-kafka.md).
You can use TiCDC to replicate incremental data from TiDB to Apache Kafka, and consume the data using Apache Flink. For details, see [Integrate with Apache Kafka and Apache Flink](/replicate-data-to-kafka.md).

## Integrate with Microsoft Fabric

You can use TiCDC to replicate incremental data from TiDB to Microsoft Fabric. With [open mirroring](https://learn.microsoft.com/en-us/fabric/mirroring/open-mirroring), TiCDC writes change data directly to a mirrored database in Fabric. This enables continuous, near real-time data replication from any TiDB deployment to Microsoft Fabric OneLake, making your data readily available for AI and analytics workloads.

For details, see this blog post [How to Replicate TiDB to a Mirrored Database in Microsoft Fabric with TiCDC](https://www.pingcap.com/blog/replicate-tidb-mirrored-database-microsoft-fabric-ticdc/).