transporter

README

Compose Transporter helps with database transformations from one store to another. It can also sync from one to another or several stores.

Transporter

About

Transporter allows the user to configure a number of data adaptors as sources or sinks. These can be databases, files or other resources. Data is read from the sources, converted into a message format, and then send down to the sink where the message is converted into a writable format for its destination. The user can also create data transformations in JavaScript which can sit between the source and sink and manipulate or filter the message flow.

Adaptors may be able to track changes as they happen in source data. This "tail" capability allows a Transporter to stay running and keep the sinks in sync.

Downloading Transporter

The latest binary releases are available from the Github Repository

Adaptors

Each adaptor has its own README page with details on configuration and capabilities.

• elasticsearch
• file
• mongodb
• postgresql
• rabbitmq
• rethinkdb

Native Functions

Each native function can be used as part of a Transform step in the pipeline.

• goja
• omit
• otto
• pick
• pretty
• rename
• skip

Commands

init

transporter init [source adaptor name] [sink adaptor name]

Generates a basic pipeline.js file in the current directory.

Example

$ transporter init mongodb elasticsearch
$ cat pipeline.js
var source = mongodb({
  "uri": "${MONGODB_URI}"
  // "timeout": "30s",
  // "tail": false,
  // "ssl": false,
  // "cacerts": ["/path/to/cert.pem"],
  // "wc": 1,
  // "fsync": false,
  // "bulk": false,
  // "collection_filters": "{}"
})

var sink = elasticsearch({
  "uri": "${ELASTICSEARCH_URI}"
  // "timeout": "10s", // defaults to 30s
  // "aws_access_key": "ABCDEF", // used for signing requests to AWS Elasticsearch service
  // "aws_access_secret": "ABCDEF" // used for signing requests to AWS Elasticsearch service
})

t.Source(source).Save(sink)
// t.Source("source", source).Save("sink", sink)
// t.Source("source", source, "namespace").Save("sink", sink, "namespace")
$

Edit the pipeline.js file to configure the source and sink nodes and also to set the namespace.

about

transporter about

Lists all the adaptors currently available.

Example

elasticsearch - an elasticsearch sink adaptor
file - an adaptor that reads / writes files
mongodb - a mongodb adaptor that functions as both a source and a sink
postgres - a postgres adaptor that functions as both a source and a sink
rabbitmq - an adaptor that handles publish/subscribe messaging with RabbitMQ 
rethinkdb - a rethinkdb adaptor that functions as both a source and a sink

Giving the name of an adaptor produces more detail, such as the sample configuration.

Example

transporter about postgres
postgres - a postgres adaptor that functions as both a source and a sink

 Sample configuration:
{
  "uri": "${POSTGRESQL_URI}"
  // "debug": false,
  // "tail": false,
  // "replication_slot": "slot"
}

run

transporter run [-log.level "info"] <application.js>

Runs the pipeline script file which has its name given as the final parameter.

test

transporter test [-log.level "info"] <application.js>

Evaluates and connects the pipeline, sources and sinks. Establishes connections but does not run. Prints out the state of connections at the end. Useful for debugging new configurations.

flags

-log.level "info" - sets the logging level. Default is info; can be debug or error.

Building Transporter

Essentials

go build ./cmd/transporter/...

Building guides

macOS Windows Vagrant

Transporter Resources

• Transporter Wiki
• Compose's articles

Contributing to Transporter

Want to help out with Transporter? Great! There are instructions to get you started here.

Licensing

Transporter is licensed under the New BSD License. See LICENSE for full license text.

Support and Guarantees

Compose does not provide support nor guarantee stability or functionality of this tool. Please take adequate caution when using Transporter to ensure that it's the right tool for the job. Transporter may not account for failure scenarios that could lead to unexpected behavior. Always take backups, always test in dev, and always feel free to submit a PR with enhancements, features, and bug fixes.