Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,16 @@ Getting there is a two-step process: model the Service Bus resources in your App

</Steps>

## Use with messaging frameworks

With Aspire managing the Azure Service Bus resource and providing connection information, you can layer a higher-level messaging framework such as [MassTransit](https://masstransit.massient.com/) or [NServiceBus](https://particular.net/nservicebus) on top.
Comment thread
jasontaylordev marked this conversation as resolved.
Building on the raw Service Bus connection, these frameworks add capabilities like message handlers, recoverability, sagas, and transactional outbox support, while Aspire continues to handle the resource lifecycle and connection wiring underneath.

For example, the [Particular Service Platform Aspire integration](https://docs.particular.net/platform/aspire/) can orchestrate NServiceBus endpoints and supporting Service Platform components alongside the Azure Service Bus resource.

## See also

- [Azure Service Bus documentation](https://learn.microsoft.com/azure/service-bus-messaging/)
- [Azure Service Bus Emulator overview](https://learn.microsoft.com/azure/service-bus-messaging/overview-emulator)
- [Sample using MassTransit with Aspire](https://github.com/MassTransit/Sample-Aspire)
- [Particular Service Platform with Azure Service Bus in Aspire (sample)](https://docs.particular.net/samples/aspire/platform-asb/)
Loading