Right now, dry-events is fully synchronous.
I experience drawbacks in my app: when a single event handler fails (exception), then the whole parent workflow fails. Typically with no retry unless it’s in a job (not the case when responding to a request).
I would like to turn part or all of the events subscriptions to async without writing a specific job for each event handler.
Maybe this topic has already been thought upon by the team? If not, I am willing to contribute a general way of doing that to dry-events if the team thinks it’s a good direction.
I don’t know how to do that yet, and that would require designing a proper abstraction to be async-framework agnostic (Sidekiq or other). But if it sounds good, I would put some time into it.
