Route transaction commits through configured brokers

[Raezil]

Summary

• make Transaction.Commit provider-aware
• publish buffered transaction events to Redis, RabbitMQ, or a custom configured provider
• preserve synchronous regular-handler execution for local stores
• on broker failure, retain only the failed/unpublished suffix so retries do not duplicate confirmed publishes
• update README.MD, examples/README.md, and the website documentation page

Tests

Added regression coverage for:

• provider-backed commits bypassing local handlers while preserving event order
• retry behavior after a partial broker publish failure

Documentation

The README and website docs now explain that transactions buffer locally until Commit, then follow the parent EventStore transport:

• no provider → execute regular handlers synchronously
• configured provider → publish buffered events to the provider; handlers run later through Consume
• partial broker failure → retry starts from the first unpublished event

Behavior

A transaction still buffers events locally until Commit. At commit time, the parent EventStore decides the execution path:

• no provider → execute regular handlers synchronously, as before
• configured provider → publish buffered events to the provider; handlers run later through Consume

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
goeventbus	Ready	Preview	Oct 4, 2026 6:24pm UTC
goeventbus-website	Canceled		Oct 4, 2026 6:24pm UTC