Messages metadata

Messages metadata

Messages used for aggregates \ sagas \ custom handlers communication now are enveloped with metadata
containing correlation id, casuation id and procesing history for better debuggin and tracing.
All event produced by command, even produced by sagas raised, can be tracked by command correlation id.
details

Event adapters merge

Event adapters for whole messages and only for nested objects are registered in one place - GridNode.EventAdaptersCatalog before Node start.

Customizable pools for actor routing

When creating a route for messages, it is possible to choose a pool - non, random, consistent hashing

No pool for aggregates and sagas

Sagas and Aggregates persistence hubs no longer use a consistenet hashing pool due to a lot of side-effects.
Now only one hub per aggregate \ saga type is existed and passes messages to its children.