# Glossary ### 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.adiom.io/basics/how-it-works/glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.