Back to Tech landscape

RabbitMQ

Cloud & DevOps

Self-hosted message broker option

Official documentation (opens in a new tab)

Overview

RabbitMQ is a supported MassTransit transport for development, on-premises, and environments where Azure Service Bus is not used. Factory docs list it as an alternative to ASB.

Microsoft Azure is our primary cloud: Factory templates deploy to App Service, AKS, Container Apps, and managed data services with Bicep or Pulumi, Azure DevOps pipelines, and Application Insights baked in from day one.

When engagements require hybrid or multi-cloud tooling, we adopt it with explicit landing zones, least-privilege identities, and runbooks—while keeping Azure the anchor for ConnectSoft-generated platforms.

From first commit to production dashboards, our DevOps path favors repeatable infrastructure, managed identities, and measurable SLOs—so releases stay boring in the best way.

Why we use it:

  • MassTransit RabbitMQ transport in templates
  • Common in Docker Compose dev stacks
  • Full control for on-prem deployments
  • Azure Service Bus preferred in cloud
  • Infrastructure as code with environment-specific parameters
  • Managed identities and private networking in production paths
  • Integrated CI/CD through Azure DevOps and quality gates

Ready to work with us?

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