MySQL workflows / Cupcake-DRCP for macOS
MySQL CDC, with the target in view.
MySQL change data capture (CDC) follows changes after the initial copy. Cupcake-DRCP brings the snapshot, capture settings, stream activity, and data comparison into one native Mac workspace.
What does MySQL change data capture do?
A snapshot copies a starting dataset. CDC follows subsequent changes so the target can continue receiving source activity. In a binlog workflow, the MySQL binary log supplies the change events; that is different from repeatedly copying every table.
Use CDC when a reporting database, downstream system, or second environment needs ongoing updates. Cupcake supports MySQL-to-PostgreSQL replication as well as supported MySQL workflows. The table mappings, source configuration, and selected capture method determine how the work runs.
Choose a capture method your source supports.
Cupcake offers MySQL binlog capture and primary-key sweep. Binlog capture depends on source logging configuration, account privileges, and available log history. A primary-key sweep reads row ranges; its scanning cost and change coverage need to be evaluated against your workload.
Review the app’s readiness checks instead of treating an ordinary successful connection as proof that CDC is ready. For source configuration, consult the MySQL binary logging reference. Set delete behavior deliberately and verify it with your chosen method.
Start with a baseline you can verify.
- Define the plan. Save your connections and review table pairs, primary keys, column mappings, and filters.
- Copy the baseline. Run a MySQL snapshot, inspect the outcome, and check the target before starting the stream.
- Start and inspect CDC. Review source readiness, stream status, checkpoints, and any errors. Coordinate the snapshot-to-capture handoff for your selected workflow.
- Compare the data. Look for missing, extra, or changed rows within the mapped scope. Investigate the cause before authorizing repair.
Follow the MySQL CDC setup guide for macOS for the full sequence.
Monitor activity and check consistency separately.
Stream activity shows that work is happening. A data comparison tells you whether the checked source and target rows agree. Use scheduled MySQL comparisons to make verification repeatable, then review any drift before applying changes.
The Mac engine operates while your Mac is awake and you are logged in. CDC requires a paid Mac license. If you need a Linux server and a shared operations console, explore Enterprise CDC monitoring.