Getting Started

Existing DB CDC roadmap

The current public path is live-read external mappings. CDC/mirrored subsets are private preview/hardening work that needs production monitoring, cleanup, and signoff before broader use.

Overview

Use live-read external mappings today. Synapsor can govern selected Postgres/MySQL rows at capability runtime without copying your whole database.

CDC is change data capture. In the private preview path, Synapsor consumes Postgres WAL/logical replication or MySQL row binlog events and maintains selected mirrored rows for governed retrieval, evidence, and replay.

Production CDC is not just a switch. The codebase has preview/dev-test primitives, but customer production CDC still needs replication credentials, lag alerts, backpressure, retention controls, slot/binlog cleanup, restore semantics, idempotent replay, and a documented disable path.

The public demo repos show the intended developer shape with local/dev fixtures. They are private preview reference material, not a claim that controlled beta runs customer CDC mirrors today.

External DB modes CDC glossary Live-read existing DB quickstart Postgres preview repo MySQL preview repo

Developer notes

Connect existing databases with live-read mappings first.
Do not connect CDC to sensitive production data during controlled beta.
Use proposal writeback for approved changes.
Treat CDC example repos as private preview material until production controls are documented as ready.

Current vs future

cdc-roadmap.txt

Current:
  live_read external mappings
  proposal writeback through trusted worker

Private preview:
  selected cdc_mirror subsets
  async catch-up from Postgres WAL or MySQL row binlog
  lag/backpressure/retention/cleanup controls

Not current:
  customer production CDC mirrors
  bidirectional replication
  raw model write access to Postgres/MySQL