Carries the events the components communicate through, rather than the
components calling each other directly. Workers emit events as a run
progresses, and the control plane folds them into run state.
Within a run, the pipeline handles batching, writing, integrity
verification, and checkpoint advancement — so an interrupted run resumes
where it left off rather than starting over. See Integrity &
checkpoints for how that works, and
Replication modes for the read strategies a
source can use.
Connectors, the data store, and the event bus are all interfaces with
swappable implementations. A connector self-registers via a blank import —
see Building a connector
to add one.
