GlueSync NoSQL to NoSQL
GlueSync uses the Eventing service provided by Couchbase to achieve the native JSON document change-tracking feature to catch field-level changes in documents in buckets on Couchbase Server 5.5 and above. We worked jointly with the Couchbase engineering team to meet both design and great performance goals to achieve the best-in-class native integration with Couchbase Server, officially supported by the vendor.
GlueSync uses always the latest SDKs provided directly by Couchbase to perform all the operations needed for the sync process. Having this kind of approach means that we are not going to face any deprecations or incompatibility issue, having choosed a native and robust approach with that technology thanks to our strategic alliance with the vendor.
Here in the following diagram is represented an architectural overview of the environment you are going to have after having deployed GlueSync.
The Eventing service should be deployed and available into your Couchbase cluster before running GlueSync. For sizing questions about how to dimension properly your cluster with this new service we recommend to reach us via mail or contact directly the Couchbase colleagues who can manage to properly help you on sizing the Eventing service based on your specific goals. We recommend to reserve for the Eventing service at least a minimum of 512 Mb of RAM before starting any production workload.
Regarding the deployment of the Eventing functions, GlueSync manages deploying and update of each function needed automagically but that is deeply discusses here at this page.
I have got a Couchbase Sync Gateway running on the same bucket in which i would like to run GlueSync, is it supported? Sure, GlueSync has been specifically design to work even within the Sync Gateway running on same data buckets.
Having further questions? For more information regarding GlueSync please reach us via email by pressing here: Contact MOLO17.