MariaDB to GCS
real-time replication
TwinCommit replicates MariaDB to Google Cloud Storage in real time by reading the MariaDB transaction log and applying every committed change exactly once and in commit order. Use it to land live MariaDB data in GCS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
MariaDB
log reader
commit-ordered · exactly-once
GCS
native writer
How capture works on MariaDB
TwinCommit reads the row-based binary log as a replica using MariaDB GTIDs, and follows Galera cluster failover automatically.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓REPLICATION SLAVE and BINLOG MONITOR grants
- ✓log_slave_updates on Galera nodes
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 MariaDB → GCS in four steps
- 1
Prepare MariaDB
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: mariadb
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]MariaDB to GCS replication FAQ
How does TwinCommit replicate MariaDB to GCS?
+
TwinCommit reads changes from the MariaDB 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 MariaDB to GCS replication need triggers or capture tables?
+
No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.
Is MariaDB 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 MariaDB versions are supported?
+
MariaDB 10.6, 10.11, 11.x · Galera Cluster · SkySQL · Amazon RDS for MariaDB.
Stream MariaDB to GCS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.