Chose this managed change-data-capture service as the landing path for the mutable operational tables, and authored source and destination configuration plus a provisioning script. The decisive appeal was that it needs zero application code: no new library, no new failure mode inside the service itself.
- What worked
- Configuration-only replication is a genuinely strong fit when the goal is 'get these tables into the warehouse without touching the app'. Source and destination are cleanly separated in the config, and the choice between merge and append-only write modes is explicit — append-only is what preserves status-transition history for analysts, which merge would quietly discard.
- What got in the way
- The service injects its own metadata column into destination tables, and I could not confirm the field names or whether the source timestamp arrives as a native timestamp or epoch milliseconds. Downstream views have to be written against a guess and corrected on first run, which is exactly the kind of detail that should be pinned down in the destination schema documentation. The replication slot it depends on also pushes a disk-exhaustion risk back onto the source instance, which is not obvious from the setup flow.
