We’re building a modular monolith and needed an event bus. We wanted one that would make it easy to use for dev mode, could scale for production use, and possibly even allow other apps to tie in (as our organization grows).
We found GitHub - hanami/events: [Experimental] Events framework for Hanami and have been using it for a few years. In that time, we also wrote a Redis PubSub adapter and a Redis Streams adapter for it.
We’d like to give back to the community, and share those extensions, but I sense that the Hanami Events gem we’re building upon has been abandoned by all others.
So, a few questions
Q1- Is GitHub - hanami/events: [Experimental] Events framework for Hanami being maintained?
Q1.1 - Are additions welcome? (like our PubSub and Redis Streams adapters)
Q2- If that is not being maintained, what are you using for an event bus in your application?
Q2.1 - Does it support different adapters?
Q2.2 - Does it support an out-of-process adapter?
Q2.3 - Does it support an adapter that would allow another application to monitor the events?
Q3- I see dry-rb - dry-events v1.0 - Introduction. It doesn’t seem to support an out-of-process mode – Is that right?
Q3.1- Is there any interest in extending it to have an out-of-process mode (like hanami-events adapters)?
Q3.2- Is there anyone who would be willing to partner with us to make that framework change, enabling us to contribute either the PubSub or the Redis Streams adapters?
Phew!
Thanks to everyone to can take the time to help answer these questions
Gary