Thanks for the cool tutorial. I have a question regarding asynchronous part. So when i publish an event, subscriber is called inside the same thread? Or will it spawn new thread somehow. Ie how async part is achieved?
As I understand it, ActiveSupport::Notifications and dry-events do not have async capabilities and are fully synchronous. Nevertheless, it seems that wisper can handle events asynchronously based on the information on its GitHub page (github.com/krisleech/wisper#handli...), although I haven't had the chance to try it myself. In our project we use ActiveSupport::Notifications, and to deal with the lack of async support, we run separate async jobs from the subscription.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the cool tutorial. I have a question regarding asynchronous part. So when i publish an event, subscriber is called inside the same thread? Or will it spawn new thread somehow. Ie how async part is achieved?
As I understand it,
ActiveSupport::Notificationsanddry-eventsdo not have async capabilities and are fully synchronous. Nevertheless, it seems thatwispercan handle events asynchronously based on the information on its GitHub page (github.com/krisleech/wisper#handli...), although I haven't had the chance to try it myself. In our project we useActiveSupport::Notifications, and to deal with the lack of async support, we run separate async jobs from the subscription.