Kafka topic
orders
A CONFIRMED order enters the stream.
A local, version-pinned lab: publish an order to a Kafka-compatible broker, filter it in EventOre, and retrieve it from a RabbitMQ queue.
Use this walkthrough to evaluate cross-broker forwarding. It uses Redpanda's Kafka API, RabbitMQ, and EventOre 0.2.1. Prerequisites: Docker with Compose, curl, and available ports 8080, 8088, and 15672. Commands use a POSIX shell; on PowerShell use curl.exe and adapt line continuations.
orders
A CONFIRMED order enters the stream.
Filter the payload and add the x-origin header.
warehouse.orders
Retrieve and inspect the forwarded message.
Download bridge-compose.yaml into an empty directory. This example uses published images; no source build is needed.
docker compose -f bridge-compose.yaml up -d
docker compose -f bridge-compose.yaml psWait for the brokers and backend to become healthy. Open the console at localhost:8088. The lab binds exposed ports to localhost and uses disposable credentials. It is not a production deployment.
docker compose -f bridge-compose.yaml exec kafka rpk topic create orders -X brokers=kafka:9092
curl -u eventore:eventore -X PUT http://localhost:15672/api/queues/%2F/warehouse.orders \
-H "Content-Type: application/json" -d '{"durable":true}'curl -X POST http://localhost:8080/api/v1/connections \
-H "Content-Type: application/json" \
-d '{"name":"lab-kafka","protocol":"KAFKA","brokerUrl":"kafka:9092"}'
curl -X POST http://localhost:8080/api/v1/connections \
-H "Content-Type: application/json" \
-d '{"name":"lab-rabbitmq","protocol":"RABBITMQ","brokerUrl":"amqp://rabbitmq:5672","credentials":{"username":"env:LAB_RABBITMQ_USER","password":"env:LAB_RABBITMQ_PASSWORD"}}'The connection stores environment-variable references. The Compose file supplies those variables to the backend; do not replace the password reference with plaintext.
Copy each response's id. Replace SOURCE_ID and TARGET_ID below. Container connections use broker service names; localhost inside EventOre would point back to its own container.
curl -X POST http://localhost:8080/api/v1/bridges \
-H "Content-Type: application/json" \
-d '{"name":"confirmed-orders","sourceConnectionId":"SOURCE_ID","sourceDestination":"orders","targetConnectionId":"TARGET_ID","targetDestination":"warehouse.orders","payloadFilter":"CONFIRMED","headerTransform":{"x-origin":"eventore-lab"},"loopPrevention":true,"autoStart":true}'Save the returned bridge id. Confirm stats.state is RUNNING. Allow the Kafka consumer to initialize before publishing; this demonstration does not backfill historical records.
curl -X POST http://localhost:8080/api/v1/connections/SOURCE_ID/kafka/publish \
-H "Content-Type: application/json" \
-d '{"destination":"orders","payload":"{\"orderId\":\"demo-1001\",\"status\":\"CONFIRMED\"}"}'
curl http://localhost:8080/api/v1/bridges/BRIDGE_ID
curl -u eventore:eventore -X POST http://localhost:15672/api/queues/%2F/warehouse.orders/get \
-H "Content-Type: application/json" \
-d '{"count":5,"ackmode":"ack_requeue_true","encoding":"auto","truncate":50000}'Expect the order payload in RabbitMQ, an x-origin header of eventore-lab, and an increase in stats.totalReplicated. The queue-read request requeues messages, so repeating it can show the same message. Publish a second order with status PENDING: the filter should exclude it.
This example uses the Kafka-specific publish endpoint. In 0.2.1, the generic publish endpoint can return HTTP 501 when automatic trace-header injection is enabled. Use the Kafka endpoint for this lab.
stats.lastError and stats.errorsCount, then inspect docker compose -f bridge-compose.yaml logs eventore-backend.curl -X POST http://localhost:8080/api/v1/bridges/BRIDGE_ID/stop
docker compose -f bridge-compose.yaml down -vThe cleanup command removes this lab's containers and volumes. Bridge state is in memory; restarting EventOre requires recreating the bridge. For delivery guarantees, persistence limits, and header caveats, read the bridge reference. For a deployment with authentication, follow the Kubernetes deployment guide.