Small database change tracking can become too much server work
A small needs to send row changes from a few to a webhook. Using Debezium can require running Kafka, Zookeeper, and alongside it.
That can turn a simple need into a much larger server setup than expected. The practical question is whether change data capture is always this heavy at small scale, or whether a simpler path can handle the job.
Key points
- The need is to stream row changes from a few tables to a webhook.
- Debezium may require Kafka, Zookeeper, and to run properly.
- That stack can feel oversized for a small project.
- On a , each extra service adds memory use and work.
- Simpler options may be enough unless exact, reliable change data capture is required.