Back to Tech landscape

NServiceBus

Backend

Alternative messaging framework

Official documentation (opens in a new tab)

Overview

NServiceBus is available when teams prefer Particular Software patterns. Templates support it via feature flags; MassTransit remains the default for new Factory and SaaS work.

Factory templates and SaaS platform programs standardize on .NET 10, Clean Architecture, and Azure-native services—so generated solutions inherit consistent security, observability, and upgrade paths instead of one-off frameworks.

When a client estate or integration boundary calls for this technology, we wire it with explicit ownership, contract tests, and telemetry—without diluting the Factory baseline your long-term platform depends on.

Planning a backend on Azure with predictable releases? Our stack choices are documented, template-backed, and ready to extend—talk to us about mapping your domain to a production-grade .NET platform.

Why we use it:

  • Optional module in microservice templates
  • Mature saga and messaging patterns
  • Coexists with ConnectSoft.Extensions packages
  • Choose when client standards require NServiceBus
  • Aligns with ASP.NET Core hosting and OpenAPI contracts in our templates
  • Observability hooks for Application Insights and OpenTelemetry
  • Clear Factory default versus client-specific adoption boundaries

Ready to work with us?

Let's discuss how our team can help achieve your digital goals