Adiom | Documentation
HomeContactDownload
  • Adiom
  • Getting Started
    • Quickstart
      • From Cosmos DB to MongoDB
      • From Cosmos DB to /dev/null
      • From on-premise MongoDB to Cosmos DB
      • From DynamoDB to Cosmos DB NoSQL
    • What is supported
  • Data Migration
    • Step By Step
  • Basics
    • Features
    • How it works
      • Sync
      • Glossary
    • Limitations
    • FAQs
  • Implementation Details
    • Architecture
    • Verification
    • Resumability
Powered by GitBook
On this page
  • Flow
  • Read Plan
  • Connector
  • Coordinator
  • Metadata store
  1. Basics
  2. How it works

Glossary

Commonly used glossary terms and definitions

PreviousSyncNextLimitations

Last updated 8 months ago

Dsync is currently in beta and is undergoing active development and testing.

Flow

Flow refers to the sequence of processes through which data moves from the source to the destination, started and managed by dsync. A flow is uniquely defined by the combination of the source, the destination and flow options (such as namespaces included).

Read Plan

A flow task plan essentially defines the flow status. The task plan requested from the source at the start of the flow includes the status of each task indicating whether they have been completed or not. The status is continiously updated throughout the flow execution. For resumable flows, the read plan is persisted in the metadata store.

Connector

Part of dsync. The source and destination connectors attach to each respective database and responds to commands from the coordinator. It manages connections to read data from the source database and write it to the destination database.

Coordinator

Part of dsync. The coordinator coordinates commands to manage the overall data flow between the connectors.

Metadata store

External database. The coordinator uses the metadata store to persist and retrieve the flow state and the task plan. This will default to the destination if not provided.