Read this tutorial on Signadot docs .
Sandboxes route a request to the right version of a service by its routing key , which travels in request headers. Change data capture breaks that chain twice. The service that handles the request only writes a row, and Debezium publishes the event later from the database's write-ahead log, without ever seeing the request.
This tutorial shows how to get the routing key through anyway. An orders service writes orders to Postgres, Debezium publishes each change to Kafka, and a fulfillment consumer reads the changes and calls a notifier . You fork each service into a sandbox and watch every change reach the right version of each service. Postgres, Debezium and Kafka stay shared: you never fork them.
Full source: signadot/examples/debezium-cdc-tutorial
How the routing key gets through the database
The request reaches orders with the routing key in its baggage header.…