Affects
Teams integrating with Midaz that need to react to ledger events — reconciliation, notifications, downstream projections, and analytics — instead of polling the REST API. This includes both self-hosted deployments that own their broker and external / SaaS integrators consuming events through a managed edge. This is a new documentation change. It describes existing event-delivery capabilities; no new product behavior is introduced.
What changed
A new reference guide, Receiving events from Midaz, is now available. It covers the two supported ways to consume the Midaz event stream and how to choose between them.
RabbitMQ direct
Bind your own queue directly to Midaz’s AMQP (0-9-1) topic exchanges. Best for self-hosted or co-located deployments where you operate the Midaz broker. The guide documents the relevant exchanges and the self-hosted environment flags that enable them.Streaming Hub
Subscribe through Lerian’s managed fan-out service via a control-plane REST API, with delivery over Webhook, Pull (HTTP), SQS, RabbitMQ, or EventBridge. Best for external / SaaS integrators who want loose coupling and per-tenant subscriptions without operating a broker.How to choose
Midaz publishes each domain event to both transports in parallel, so both surfaces expose the same underlying events. The guide includes a side-by-side comparison (transport, what you connect to, coupling, and best-fit scenarios) to help you pick the right approach.Impact
This is an informational change. No endpoints, event schemas, or delivery behavior change. Nothing to migrate and no action is required. Classification: Informational. The change is the availability of a consolidated reference for receiving Midaz events.
What you need to do
Read Receiving events from Midaz to understand the two approaches at a glance.
If you run your own Midaz broker, review the RabbitMQ direct section and the self-hosted environment flags.