A newer version of this documentation is available.
View Latest (v2.0)

Gluesync SQL to NoSQL

Targeting MongoDB

Core principles

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 issues, having selected a native and robust approach with that technology thanks to our strategic alliance with the vendor.

Gluesync needs to create its collection to store some information as sync checkpoints, document checksums and others. The collection name is GLUESYNC_STATE_PRESERVATION. You should not delete or edit this collection or its content to avoid experiencing unexpected behaviors.

Architectural overview

Here in the following diagram represents 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

Q&A

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 designed 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 is served via MongoDB Atlas DBaaS or running in any public cloud hosting service. 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.