Concepts
Understand the model one boundary at a time.
Start with the portable messaging model, then follow it down to receive endpoints, routing, dispatch, and settlement. Each page explains one concept deeply enough to operate it without turning this guide into a broker manual.
Messages and contracts
Message identity, envelopes, headers, polymorphism, and cross-language schema design.
Read concept →02 · IntentSend, publish, request
Choose an interaction from ownership and coupling—not from the broker topology.
Read concept →03 · BoundaryReceive endpoints
How one queue, one receive pipeline, and several message bindings form an operational boundary.
Read concept →04 · RouteRouting and topology
How logical messages and endpoints project to exchanges, topics, queues, and bindings.
Read concept →05 · ExecuteConsumers and dispatch
Handler matching, scopes, grouped consumer methods, concurrency, and completion semantics.
Read concept →06 · CorrelateRequests and responses
Response addresses, request identifiers, typed replies, faults, cancellation, and timeouts.
Read concept →07 · RecoverReliability and faults
Settlement, retry, redelivery, idempotency, and the error, fault, and skipped destinations.
Read concept →How the pieces connect
The most important distinction is between an endpoint and a consumer. A receive endpoint owns the queue and receive pipeline. Message bindings decide what can arrive there. Consumer registrations decide which handlers run for each delivery.
Where compatibility stops being the explanation
Familiarity with MassTransit transfers well, but MyServiceBus documents its own verified behavior and platform parity. Use the interoperability guides when the other framework is actually present on the wire; use these concept pages to understand MyServiceBus itself.