LiteBus

First-class contracts like ICommand<TResult> and IQuery<TResult> enforce Command Query Separation, making code self-documenting and intentions explicit, as shown in the quick start examples with separate command, query, and event definitions.

Distinct pre-handlers, post-handlers, and error-handlers for each message type allow fine-grained processing stages, enabling validation, logging, and error handling at specific points without monolithic behaviors.

A single handler can apply to all matching message types via generic constraints, automatically discovered during assembly registration, simplifying cross-cutting concerns like logging and metrics without per-message boilerplate.

Configurable sequential or parallel execution for event priority groups and handlers fine-tunes throughput, useful for managing complex workflows with dependent or independent side-effects.