Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TiDB binlog与ticdc区别，如何选择
|
username: 路在何chu
【TiDB Usage Environment】Production Environment
TiDB synchronizing to MySQL
【TiDB Version】
6.5
Choose TiCDC, the binlog of version 6.5 can no longer fully support all TiDB operations.
The official recommendation is to use TiCDC instead of binlog.
TiDB Binlog is incompatible with some features introduced in TiDB v5.0 and cannot be used together. For details, refer to Precautions. It is recommended to use TiCDC instead of TiDB Binlog.
If there are no large transactions, use binlog; if there are large transactions, use TiCDC.
It depends on the scenario you are using it for. If you just want to capture and parse binlogs like MySQL, then you need to use TiDB Binlog.
You can directly use CDC, analyze binlog, and directly downstream to MySQL.
When our cluster was using a lower version, we used binlog for incremental synchronization, which did not support TiCDC. Now that we have upgraded to a higher version, we are using TiCDC.
There is a small issue here: TiCDC can only synchronize with the same database name.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: