MongoDB to Databricks
real-time replication
TwinCommit replicates MongoDB to Databricks in real time by reading the MongoDB transaction log and applying every committed change exactly once and in commit order. Use it to feed Databricks with live MongoDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MongoDB
log reader
commit-ordered · exactly-once
Databricks
native writer
How capture works on MongoDB
TwinCommit opens change streams on replica sets and sharded clusters, persists resume tokens with the checkpoint, and keeps multi-document transactions intact.
Prerequisites
- ✓Replica set or sharded cluster (change streams need an oplog)
- ✓changeStream and find privileges on watched databases
- ✓Pre- and post-images enabled for full before/after values (optional)
How apply works on Databricks
Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Requirements
- ✓A SQL warehouse or all-purpose cluster
- ✓A Unity Catalog volume or external location for staging
- ✓A service principal with MODIFY on the target schema
Setup
Set up MongoDB → Databricks in four steps
- 1
Prepare MongoDB
Run twincommit check. It verifies replica set or sharded cluster (change streams need an oplog) and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Databricks
Add a target block for Databricks. 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: mongodb
uri: ${MONGODB_URI}
target:
type: databricks
host: adb-1234567890.12.azuredatabricks.net
warehouse: replication-wh
catalog: main
schema: replica
tables:
- source: sales.orders
- source: sales.customersMongoDB to Databricks replication FAQ
How does TwinCommit replicate MongoDB to Databricks?
+
TwinCommit reads changes from the MongoDB transaction log, buffers them per transaction, and applies each committed transaction to Databricks in commit order. Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Does MongoDB to Databricks replication need triggers or capture tables?
+
No. TwinCommit reads the MongoDB log directly and creates no objects in the source database.
Is MongoDB to Databricks replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Databricks transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MongoDB versions are supported?
+
MongoDB 5.0–8.x · MongoDB Atlas · replica sets and sharded clusters.
Use cases for this route
Related replication routes
Stream MongoDB to Databricks today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.