A .NET framework for building async microservices with support for multiple message queues and databases.
NServiceBus is a .NET framework for building asynchronous microservices and distributed systems. It provides abstractions over messaging infrastructure, allowing developers to focus on business logic rather than plumbing code. The framework supports multiple message queues and databases, enabling reliable communication and data persistence across cloud, on-premises, and containerized environments.
.NET developers and architects building enterprise-grade microservices, distributed systems, or message-driven applications that require reliable messaging, saga orchestration, and cross-platform deployment.
Developers choose NServiceBus for its comprehensive feature set, extensive support for various messaging and database technologies, and professional backing with 24/7 support. It reduces boilerplate code and infrastructure complexity while providing tools for monitoring, debugging, and orchestrating long-running processes.
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 (e.g., Azure Service Bus, RabbitMQ, Amazon SQS) and databases (e.g., SQL Server, PostgreSQL, Cosmos DB), offering flexibility in technology choices.
Provides native support for managing long-running business processes with sagas, reducing the need for custom state management code.
Includes 24x7 support from dedicated engineers worldwide, ensuring reliability and assistance for critical enterprise deployments.
Runs on-premises, in the cloud, in containers, or serverless, enabling diverse and scalable deployment strategies.
Uses the RPL 1.5 license, which may not be fully open-source and could involve commercial terms or restrictions for certain uses.
The comprehensive feature set and configuration for transports and persistence require significant time to master compared to simpler frameworks.
Tight integration with the Particular Service Platform may limit flexibility and make switching to alternative tools more difficult.