AI agents: use the documentation index at llms.txt to locate machine-readable pages. This section is indexed by https://docs.particular.net/transports/llms.txt. The markdown version of this page is served as plain text. An MCP server at /mcp serves the same content via the search_docs and read_doc tools; it is read-only and needs no credentials. Markdown versions of documentation pages are available by appending .md to the page URL. Directory URLs use index.md. They are served as text/plain because some retrieval backends reject text/markdown.

Transports

NServiceBus provides an abstraction for underlying queuing technologies. An implementation of that abstraction for a given queuing technology is known as a "transport".

This abstraction enables businesses to build systems with the Particular Service Platform using existing queuing technologies. Sometimes, the choice of queuing technology may be constrained by business needs. At other times, the best queuing technology can be selected according to the application's requirements. The transport abstraction allows teams to spend more time delivering business features and less time dealing with the details of a specific queuing technology.

The transport documentation describes the differences between transports and provides guidelines for deciding which transport may best suit a specific scenario. For each transport, the documentation explains how to make optimal use of NServiceBus in combination with that transport, including how to handle concurrency, transactions, scaling, and more.

How to select a transport

Initially, it can be challenging to decide which queuing technology is best for a specific scenario. See the guide to selecting a transport for help in making that decision.

Supported transports

Related Articles