MG
MongoDB
Tail change streams across replica sets and sharded clusters, with resume tokens kept for you.
category
Databases
direction
Source
method
change streams
How it works
Tail change streams across replica sets and sharded clusters, with resume tokens kept for you. Sluice tracks the position of every event, so a restart picks up exactly where it stopped and nothing is written twice.
What you get
Initial snapshot, then continuous change streams capture
Schema changes detected and versioned before they reach a destination
Replay any window from the last 30 days without touching the source
Per table lag, throughput and error metrics in the dashboard
Setup
Add MongoDB from the connector directory, paste credentials or sign in with OAuth, and pick the tables or objects to sync. The first events usually arrive within a minute.
PG
Source + destination
Postgres
CDC · logical replication
Stream every insert, update and delete from Postgres straight off the write ahead log.
MY
Source
MySQL
CDC · binlog
Row based binlog capture with no triggers and no polling queries on your primary.
KF
Source + destination
Kafka
topics · consumer groups
Read from and write to Kafka topics with offsets committed only after the destination confirms.