Incoming messages pipeline - rebus-org/Rebus GitHub Wiki

When handling received messages, everything starts with Rebus having received one single message from its configured ITransport.

When it has a message, it will add the message to an incoming step context and invoke its pipeline of incoming message steps.

Each incoming message step then has one function, e.g. one of the steps (DeserializeIncomingMessageStep) will deserialize the message and store the result in the context, making it available for the subsequent steps to use.

In a similar way, outgoing messages will be passed through an outgoing messages pipeline.

Since the contents of the two pipelines determines a pretty big part of Rebus' behavior, there's a function to log the contents of the pipelines at startup.