Anton Davydov

also, one more thing here: I think we need to use different runners for different types of events. Something like thread runner for memory async and server runner for redis...

@ianks I created PoC for runner and merged it. Do you have any ideas what we need to do next? From my perspective: middlewares and test it with other adapters....

@joelvh hey, thanks for your ideas 💯 I think, for the first iteration, we can use `SecureRandom.hex` for this ([like a in sidekiq](https://github.com/mperham/sidekiq/blob/master/lib/sidekiq/client.rb#L98)). For me, the general idea of "eid"...

yep, agree with you. that's why I suggest to create a simple solution before and understand what we need :)

I created simple backlog for this feature. will work on it

Hello! Yep, I forgot to create issue for this but in future we want to use types for each event and use it like this: ```ruby events = Hanami::Events.initialize(:memory_sync) events.subscribe('user.created')...

so, I thought about something like this: ### Event ```ruby class Users::Events::PasswordChanged < Hanami::Event::Type event_name 'user.password_changed' attribute :user_id, Types::UUID attribute :password, Types::String end ``` ### Broadcaster ```ruby password_changed = Users::Events::PasswordChanged.new(payload)...

no, it's just a mapping event for specific subscribe by version: ```ruby events = Hanami::Events.build(:memory) events.subscribe('*', version: 1.0) { |payload| puts "version 1" } events.subscribe('*', version: 2.0) { |payload| puts...

Thanks for PR 👍 But I think we need to discuss some parts and understand what we want. ---------------------------- First of all, I think we must set types as optional....

About event type: I prefere if lib will raise error if types will different. Because we need to be sure that event log will have only valid data. Again, great...