If you're moving insurance policy data from a nightly batch to an event stream, the broker is the easy part. The hard part is that insurance transactions don't arrive in the order they take effect. An endorsement processed in May can be effective in January, and a consumer that simply applies events as they land will quietly compute the wrong policy state.
The fix is structural. Partition events by policy number, store every transaction instead of overwriting state, and rebuild the policy view in effective-date order each time something changes. Below is one way to build that on Azure, along with the failure modes worth planning for before anyone writes code.
Why the nightly batch hid this problem
Batch jobs recompute everything overnight from the system of record. If a backdated change came in at 4 p.m., the 2 a.m. run picked it up and re-rated the term from scratch. Nobody downstream ever saw the in-between state.
Streaming removes that safety net.…