Idea on making the ubsubscribe in event bus not racy
Basically depends on atomic long on message creation side,
and application in order on receiving end (if received not in order,
application will be delayed until an "in order" msg arrives, so we can
unstash the previous ones)

> todo test the unsubscriber more in the new scenarios?
> rethink if cound be done less costy somehow