Dariusz Gafka

> Query handlers in projections and aggregates are boilerplate code in your concept. (...) My idea is to replace the default connection for all query handlers and do not specify...

Ecotone does not control DI Services from the Application (how `InProgressTicketList` is registered in DI). In this example Redis could be used as Read Model for example, which would not...

> If the query handler is used in a command handler You mean like you trigger and Query Bus inside your Command Handler to check the logic?

You could wire up your own attribute which would inject specific Connection. The default one keep write and the read one would be used by attribute ```php #[Attribute(Attribute::TARGET_PARAMETER)] final class...

You could wire up Service an do something like that: ```php class ConnectionResolver { public function resolve(): Connection { if ($this->connection->isInTranscation()) { return $this->writeConnection; } return $this->readConnection; } } ```...

Closing as proposal was given that can be built from Ecotone components (however this is too application specific to be part of the Framework).

I guess deployment will differ depending on the execution platform you're using. In general the way you run Message Consumers, is most likely the same, just the box in which...

Hey @ralfkuehnel, I think make sense, feel free to open PR. Please use `ConfigurationVariableService` to fetch parameters, as this is the Service that work across different implementations (Symfony, Laravel, Ecotone...

@Ocramius are you able to help to push that forward?

Can you provide a failure test case for this?