Consider allowing integration handlers to consume events.

[jmalloc]

See also #90.

The idea here is that integrations with other systems may need to respond to events that occur, without necessarily involving a business process.

One hypothetical example would be sending a notification to online users about completion of a transaction.

[jmalloc]

@danilvpetrov Do you have any use-cases from Hive where this might apply?

[danilvpetrov]

Not at the moment, even all those events that are going to the processes should be probably kept this way as these processes guard their state and fire commands to the integration handlers accordingly. However, I can envisage the situation where some standalone integration handlers would need to listen to the events published by aggregates (even processes).

[jmalloc]

I'm closing this due to a lack of necessity. We can reopen it if we find legitimate use cases.

The example given above:

One hypothetical example would be sending a notification to online users about completion of a transaction.

Could be reasonably modelled as a projection anyway.

[jmalloc]

We've discovered a use-case for this at cwx wherein we need to push an ephemeral notification to a connected client.

/cc @mrubiosan