Installation steps

Gluesync NoSQL to NoSQL

Basic configuration example

This module can be customized by using a configuration file in JSON format. The file name to use must be specified as parameter when launching the app, with the -f or --file tokens. The file must have the following structure:

{
  "sourceHost": "NOSQL_SERVER_ADDRESS_HERE",
  "sourcePort": "18091",
  "sourceName": "bucket-name",
  "sourceUsername": "bucket-user",
  "sourcePassword": "bucket-pwd",
  "sourceEntities": {
    "orders": {},
    "DocumentType2": {},
    "DocumentType3": {},
    "DocumentType4": {},
    "DocumentType5": {}
  },

  "targetHost": "TARGET_NOSQL_SERVER_ADDRESS_HERE",
  "targetPort": "3000",
  "targetName": "db-name",
  "targetUsername": "db-user",
  "targetPassword": "db-pwd",

  "copySourceEntitiesAtStartup": true,
  "maxItemsCountPerTransaction": 100,
  "maxTransactionCountPerIteration": 100,
  "maxMigrationItemsCountPerIteration": 1000
}

The parameters that refer to a source are the parameters that describe the connection to the NoSQL instance.

sourceHost: the host where the instance is reachable from;
sourcePort: the port which the instance is reachable from;
sourceName: the name of the database in the NoSQL instance;
sourceUsername: username of a privileged user in the instance;
sourcePassword: password of such user;
sourceEntities: document types that Gluesync is going to replicate to the target database.

The parameters that refer to a target are the parameters that describe the connection to the NoSQL instance.

targetHost: the host where the instance is reachable from;
targetPort: the port which the instance is reachable from;
targetName: the name of the target database in the NoSQL instance;
targetUsername: username of a privileged user in the instance;
targetPassword: password of such user;

Other configuration parameters are the following:

copySourceEntitiesAtStartup: boolean which indicates whether Gluesync should copy the whole tables contents when launched the first time;
maxItemsCountPerTransaction: the maximum number of events that should be processed simultaneously;
maxTransactionCountPerIteration: the maximum number of transactions that should be processed when simultaneously;
maxMigrationItemsCountPerIteration: defaults to 1000, it’s the size of each chunk of data being loaded by the initial snapshot process per each one of its threads. Change that value accordingly to your specific use case needs.