Dariusz Gafka

> This PR introduces a new interface named RealMessageProcessor which will replace the actual MessageProcessor interface. This interface has only one method: process(Message $message): ?Message Why would we replace MessageProcessor?...

@jlabedo I will have more time to look on this later this week. For now, what I can leave feed for thoughts, because I just remind myself of more advanced...

> I will clean it a bit more to explain how things are working here Ok, will review after you post your final summary :)

In general very nice design and idea with this refactor. The code is more readable now and feels like allows to work with higher level of abstraction without bothering with...

I understand the need for Commands where we trigger an action from HTTP Controller. I don't see the use case for synchronous Events however. As synchronous Events are result of...

It's doable for Message Handlers, however I don't see how this solution can be stable at that level. So suppose we put ErrorChannel flag on top of one of three...

> > It's doable for Message Handlers, however I don't see how this solution can be stable at that level. So suppose we put ErrorChannel flag on top of one...

@lifinsky transaction interceptors are around interceptors, therefore they work in this manner: ```php beginTransaction(); $methodInvocation->proceed(); // Whatever is intercepted commit(); ``` And they are set up on Command Bus level,...

This is now available as Enterprise feature starting from `1.258.1` Cheers :)

Hey @lifinsky What database is used is out of the scope for `Message Handlers`. They are responsible for taking care of the flow, and what is done inside Handler is...