Paweł Pacana

Related: https://www.loom.com/share/49caaa09ded0452db024f199e20eb9ae

> We should not care for now, about aggregate being possibly inconsistent As a user you might be interested in handling that inconsistency. It is probably the easiest (at least...

> I don't like yields which are not obvious when are they happening either, ```ruby def foo(&block) block.call if block_given? end ``` I think I'd still prefer block/yield for consistency.

https://github.com/ko1/ractor-tvar STM is coming and might help here :)

I can totally feel your pain with regard to current async handlers implementation and various limitations coming from the framework it leans on: https://gist.github.com/pawelpacana/295337e92dd9edd2e443e6b31ac2683a What works for me, which can...

> perform method receives instances of the ActiveRecord-based event model Just to expand a bit: * ActiveRecord is only inside `rails_event_store_active_record` gem and its repository and it never leaves it...

Also to keep in mind, a likely direction we'll take in the future: https://github.com/RailsEventStore/rails_event_store/issues/755#issuecomment-721059147

Perhaps there's also some quick win with globalid and its support in ActiveJob: https://edgeguides.rubyonrails.org/active_job_basics.html#globalid

That said, I'm aware that async handler experience can be improved here. I'm not convinced yet with proposed implementation. I'd also be very cautious when introducing changes here — we'll...

reminder for myself: https://arkency.slack.com/archives/C7B95EW3V/p1610742307030100