MariaDB to ADLS
real-time replication
TwinCommit replicates MariaDB to Azure Data Lake 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 ADLS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
MariaDB
log reader
commit-ordered · exactly-once
ADLS
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 ADLS
Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Requirements
- ✓Storage Blob Data Contributor on the container
- ✓Hierarchical namespace enabled
- ✓Optional Iceberg catalog (REST or Hive Metastore)
Setup
Set up MariaDB → ADLS 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 ADLS
Add a target block for ADLS. 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: adls
account: acmelake
container: lake
path: replica/{schema}/{table}
format: delta
mode: merge
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MariaDB to ADLS replication FAQ
How does TwinCommit replicate MariaDB to ADLS?
+
TwinCommit reads changes from the MariaDB transaction log, buffers them per transaction, and applies each committed transaction to ADLS in commit order. Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Does MariaDB to ADLS replication need triggers or capture tables?
+
No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.
Is MariaDB to ADLS replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same ADLS 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 ADLS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.