Affects
Teams that produce or consume event streams from Fetcher, Lender, Matcher, Midaz, Reporter, or Tracer.
What changed
Kafka producers publish to documented application topics such as
lerian.streaming.ledger. Consumers subscribe to those topics and route individual facts by CloudEvents headers. Reporter uses AMQP instead: it publishes to the exchange named by RABBITMQ_REPORT_EVENTS_EXCHANGE and uses each event definition key as the routing key. Producers validate their roster source values, and CloudEvents types are source-qualified.
Matcher now publishes the topic consumed by Lender’s enabled matcher handoff. Reporter events use the reporter source; their manifests carry event keys and do not define per-event topic or dead-letter-topic fields. Reporter consumers bind queues to the configured exchange and route by the manifest event key.
This is a documentation correction of implemented contracts. It does not announce a runtime release.
Impact
Classification: Action required. Topic derivation, source configuration, event routing, or Reporter manifest handling based on the former contract can prevent delivery or route events incorrectly.
What you need to do
1
Kafka producers publish to the documented application topics. Kafka consumers subscribe to those topics and route facts by their CloudEvents headers. For Reporter, bind a queue to
RABBITMQ_REPORT_EVENTS_EXCHANGE and route by the event definition key.2
Set each producer’s documented source value and review consumer assumptions about source-qualified event types.
3
Review Matcher-to-Lender and Reporter integrations before the next streaming deployment.