Back to Tech landscape

MassTransit

Backend

Default .NET messaging with Azure Service Bus and RabbitMQ

Official documentation (opens in a new tab)

Overview

MassTransit implements integration events, sagas, consumer pipelines, and outbox patterns in ConnectSoft Factory templates. Azure Service Bus is the default transport on Azure; RabbitMQ and alternative brokers activate via configuration when client or local dev scenarios require them.

Platform libraries wrap MassTransit with Serilog enrichers for correlation IDs, health checks, and test harnesses so teams verify message flows in CI. SaaS programs include outbox tables and idempotent consumers—reducing duplicate processing risk during deploys and broker outages.

NServiceBus and raw broker SDKs remain supported at client boundaries; Factory work standardizes on MassTransit to keep observability, retry policies, and documentation consistent across services.

Event-driven architecture on Azure without reinventing middleware? MassTransit in our templates is production-proven—extend consumers while keeping transports swappable.

Why we use it:

  • Default messaging library in Factory and SaaS platform templates
  • Azure Service Bus transport with RabbitMQ as a configured alternative
  • Outbox and idempotent consumer patterns in SaaS programs
  • Serilog correlation and health checks for message pipelines
  • Saga and routing slip support for long-running workflows
  • ConnectSoft.Extensions.MessagingModel.MassTransit for shared conventions

Ready to work with us?

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