Azure Service Bus是否可用于Azure Stack？寻求本地长期消息总线替代方案

First, let's tackle your core question about Azure Service Bus and Azure Stack:

From the official Microsoft context you referenced, it’s clear that Azure Service Bus does not offer a native on-premises deployment option via Azure Stack. The focus here is on hybrid collaboration and federation—like bridging on-premises systems to Azure Service Bus using tools such as Hybrid Connections—rather than hosting the full managed Service Bus service locally on Azure Stack. Microsoft has shifted its on-premises messaging strategy toward hybrid integration instead of bringing the complete Azure Service Bus offering to local infrastructure.

Now, let’s break down recommended alternative solutions tailored to your long-term on-premises deployment needs, especially given your background with Windows Service Bus 1.1:

• Azure Service Bus Hybrid Connections
  If you’re open to a hybrid approach (instead of 100% on-premises), this is a seamless fit. It lets you connect your local services to Azure Service Bus without opening public firewall ports, keeping your workloads on-prem while leveraging Azure’s managed messaging capabilities. This maintains the familiar Service Bus pattern you’re used to and comes with long-term official support.

• NServiceBus
  Built specifically for the .NET ecosystem (aligning perfectly with your Windows Service Bus history), NServiceBus offers robust on-premises deployment options with commercial support. It supports core messaging patterns like queues, topics, and subscriptions—making migration smoother—and includes enterprise-grade features like retries, sagas, and monitoring. Ideal for teams needing reliable, mission-critical local workflows.

• RabbitMQ
  A widely adopted open-source message broker that’s easy to deploy on Windows (or any platform). It supports multiple protocols (AMQP, MQTT, HTTP) and has a strong, active community. RabbitMQ offers high availability, clustering, and flexible routing, making it a solid choice for teams wanting a free, customizable on-prem solution with extensive documentation and integrations.

• Apache Kafka
  If your workload involves high-throughput streaming or big data use cases, Kafka is a top pick. Designed to handle massive message volumes with low latency, it supports on-prem deployment across Windows, Linux, and macOS. While it leans more into stream processing than traditional enterprise messaging, it’s a scalable long-term solution if you need to handle larger workloads than traditional brokers can manage.

• ActiveMQ Artemis
  An enterprise-grade open-source broker from Apache, with native support for AMQP, MQTT, and STOMP. It’s lightweight, high-performance, and includes essential features like high availability, disaster recovery, and message persistence. It integrates well with .NET apps and has a straightforward setup process for Windows environments.

Content of the question originates from Stack Exchange, asked by MiltonSwingline