MySQL to GCS
real-time replication
TwinCommit replicates MySQL to Google Cloud Storage in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to land live MySQL data in GCS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
MySQL
log reader
commit-ordered · exactly-once
GCS
native writer
How capture works on MySQL
TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓GTID mode recommended
- ✓REPLICATION SLAVE and REPLICATION CLIENT grants
How apply works on GCS
Changes land as Apache Iceberg, Delta Lake or Parquet tables with one atomic commit per micro-batch. Iceberg tables register in the BigLake metastore so BigQuery can query them in place.
Requirements
- ✓Storage Object Admin on the bucket
- ✓BigLake Admin for catalog registration (optional)
- ✓Workload identity or a service-account key
Setup
Set up MySQL → GCS in four steps
- 1
Prepare MySQL
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at GCS
Add a target block for GCS. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mysql
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: gcs
bucket: acme-lake
path: replica/{schema}/{table}
format: iceberg
catalog: { type: biglake, project: acme-analytics }
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MySQL to GCS replication FAQ
How does TwinCommit replicate MySQL to GCS?
+
TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to GCS in commit order. Changes land as Apache Iceberg, Delta Lake or Parquet tables with one atomic commit per micro-batch. Iceberg tables register in the BigLake metastore so BigQuery can query them in place.
Does MySQL to GCS replication need triggers or capture tables?
+
No. TwinCommit reads the MySQL log directly and creates no objects in the source database.
Is MySQL to GCS replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same GCS transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MySQL versions are supported?
+
MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.
Stream MySQL to GCS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.