Gluesync NoSQL to NoSQL

Replicate data from MongoDB

Core principles

Gluesync uses the Change Streams feature provided by MongoDB to catch real-time data changes in JSON documents in MongoDB databases and collections starting from MongoDB 3.6 and above.

To perform all the operations under MongoDB, Gluesync uses the latest SDKs provided directly by MongoDB. Having this kind of approach means that we are not going to face any deprecations or incompatibility issue, having selected a native and robust approach with that technology thanks to our strategic alliance with the vendor.

Gluesync needs to create own collection to store some informations as sync checkpoint, documents checksums and others. The collection name is GLUESYNC_STATE_PRESERVATION. Don’t delete or edit this collection or its content.

Architectural overview

Here in the following diagram is represented an architectural overview of the environment you are going to have after having deployed Gluesync.

a diagram illustrating the architectural overview of Gluesync for MongoDB


I have got MongoDB Realm running on the same database in which i would like to run Gluesync, is it supported? Sure, Gluesync has been specifically design to work even within MongoDB Realm running on the same database.

I have got MongoDB running under MongoDB Atlas DBaaS, is it supported? Gluesync works great even when your MongoDB in served via MongoDB Atlas DBaaS or running in any public cloud hosting services. Have a look at Deploying in MongoDB Atlas DBaaS for further details on how to configure it.

Having further questions? For more information regarding Gluesync please reach us via email by pressing here: Contact MOLO17.