A .NET framework for building async microservices with message-based communication, supporting multiple cloud providers and on-premises deployment.
NServiceBus is a .NET framework for building asynchronous, message-driven microservices and distributed systems. It provides abstractions over messaging infrastructure, enabling developers to implement reliable communication patterns without writing low-level plumbing code. The framework supports multiple message queues and databases while offering tools for monitoring, debugging, and managing long-running business processes.
.NET developers and architects building enterprise-scale microservices, distributed systems, or message-based applications that require reliable communication across cloud, on-premises, or hybrid environments.
Developers choose NServiceBus for its comprehensive approach to messaging infrastructure, reducing boilerplate code while providing enterprise-grade reliability, observability tools, and professional support. Its flexibility across multiple cloud providers and on-premises deployments makes it suitable for complex, scalable systems.
The gold standard for async .NET microservices on Azure, AWS and on-prem
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports multiple message queues like Azure Service Bus, RabbitMQ, and Amazon SQS, and databases including SQL Server and Cosmos DB, offering deployment flexibility across cloud and on-premises.
Includes built-in saga patterns for managing long-running business processes, reducing the need for custom workflow code in distributed systems.
Provides Open Telemetry integration and is part of the Particular Service Platform for monitoring and debugging, enhancing system reliability.
Backed by 24x7 professional support and comprehensive documentation, reducing operational risks for enterprise applications.
Licensed under RPL 1.5, which is less permissive than standard open-source licenses and may involve costs for commercial use, as indicated in the README.
Requires configuring multiple message queues and databases, with tutorials assuming enterprise-scale knowledge, making it daunting for smaller projects.
Tight integration with the Particular Service Platform tools for monitoring and debugging can create dependency, limiting flexibility with third-party solutions.