Cross-broker message replication
Forward messages between configured brokers, filter payloads, and transform headers with EventOre.
A bridge connects one source connection and destination to one target connection and destination. Both providers must be included in the backend image. For a complete local example, follow the Kafka to RabbitMQ tutorial.
How a bridge works
The backend manages the subscription and records successful publishes, bytes, and errors. An accepted create request does not prove end-to-end delivery; inspect the target broker and bridge statistics.
Create a bridge
Replace the connection IDs with IDs returned by the connections API. These are the request fields supported in 0.2.1:
curl -X POST http://localhost:8080/api/v1/bridges \
-H "Content-Type: application/json" \
-d '{"name":"orders-to-warehouse","sourceConnectionId":"SOURCE_ID","sourceDestination":"orders","targetConnectionId":"TARGET_ID","targetDestination":"warehouse.orders","headerTransform":{"x-origin":"orders-demo"},"payloadFilter":"CONFIRMED","loopPrevention":true,"autoStart":false}'Creation returns HTTP 201 and an id. Add your configured bearer token to requests when API authentication is enabled. Creating and changing bridges requires a deployment mode that permits connection management.
Test a filter without publishing
curl -X POST http://localhost:8080/api/v1/bridges/test \
-H "Content-Type: application/json" \
-d '{"payload":"{\"status\":\"CONFIRMED\"}","headers":{},"payloadFilter":"CONFIRMED","headerTransform":{"x-origin":"orders-demo"},"loopPrevention":true}'The response includes passedFilter, loopDetected, transformedHeaders, transformedPayload, and filterReason. A dry run checks transformation rules; it does not test broker connectivity or deliver a message.
Start, inspect, and stop
curl -X POST http://localhost:8080/api/v1/bridges/BRIDGE_ID/start
curl http://localhost:8080/api/v1/bridges/BRIDGE_ID
curl -X POST http://localhost:8080/api/v1/bridges/BRIDGE_ID/stop
curl -X DELETE http://localhost:8080/api/v1/bridges/BRIDGE_IDStatistics include totalReplicated, bytesReplicated, errorsCount, lastError, and state. The API offers start and stop operations; it has no separate pause endpoint.
Header rules and filters
payloadFilteruses Java regular-expression matching withfind(), not JSONPath.headerTransformsets headers. Keys prefixed withrename:rename existing headers;remove:removes them.- Loop detection uses
x-eventore-bridge-idandx-eventore-replicated. Keep these reserved headers intact. Loop protection depends on providers preserving headers; do not assume it works across every protocol or multi-hop topology.
Delivery and lifecycle limits
Bridge definitions, runtime state, and counters are held in the backend process. Restarting it loses bridge definitions. External connection persistence does not persist bridges or provide automatic bridge failover. There is no bridge-level durable retry queue or exactly-once guarantee. Validate source acknowledgement behavior and target delivery before adopting a workflow.
Try the Kafka → RabbitMQ lab · Authentication and configuration · Troubleshooting