您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

服务总线高级和标准消息传送层Service Bus Premium and Standard messaging tiers

服务总线消息传送(包括队列和主题等实体)将企业消息传送功能与丰富的云规模发布-订阅语义结合在一起。Service Bus Messaging, which includes entities such as queues and topics, combines enterprise messaging capabilities with rich publish-subscribe semantics at cloud scale. 对于许多完善的云解决方案,服务总线消息传送会用作通信基础结构。Service Bus Messaging is used as the communication backbone for many sophisticated cloud solutions.

服务总线消息传送的高级层将解决有关任务关键应用程序的规模、性能和可用性的常见客户请求。The Premium tier of Service Bus Messaging addresses common customer requests around scale, performance, and availability for mission-critical applications. 高级层建议用于生产方案。The Premium tier is recommended for production scenarios. 虽然功能集几乎完全相同,但这两个层的服务总线消息传送旨在用于满足不同的使用情形。Although the feature sets are nearly identical, these two tiers of Service Bus Messaging are designed to serve different use cases.

下表突出显示了部分高层差异。Some high-level differences are highlighted in the following table.

高级Premium 标准Standard
高吞吐量High throughput 可变吞吐量Variable throughput
可预测性能Predictable performance 可变滞后时间Variable latency
固定价格Fixed pricing 即用即付可变定价Pay as you go variable pricing
可以扩展和缩减工作负荷Ability to scale workload up and down 不适用N/A
消息大小最大为 1 MBMessage size up to 1 MB 消息大小最大为 256 KBMessage size up to 256 KB

服务总线高级消息传送在 CPU 和内存级别提供资源隔离,以便每个客户工作负荷以隔离方式运行。Service Bus Premium Messaging provides resource isolation at the CPU and memory level so that each customer workload runs in isolation. 此资源容器称为 消息传送单元This resource container is called a messaging unit. 每个高级命名空间至少会分配一个消息传送单元。Each premium namespace is allocated at least one messaging unit. 可以为每个服务总线高级命名空间购买 1、2 或 4 个消息传送单元。You can purchase 1, 2, or 4 messaging units for each Service Bus Premium namespace. 单一工作负荷或实体可以跨多个消息传送单元,尽管计费以 24 小时或每天的费率收取,但仍然可以随意更改消息传送单元数。A single workload or entity can span multiple messaging units and the number of messaging units can be changed at will, although billing is in 24-hour or daily rate charges. 从而为基于服务总线的解决方案提供可预测和稳定的性能。The result is predictable and repeatable performance for your Service Bus-based solution.

此性能不仅更易于预测和实现,而且速度更快。Not only is this performance more predictable and available, but it is also faster. 服务总线高级消息传送以在 Azure 事件中心引入的存储引擎为基础。Service Bus Premium Messaging builds on the storage engine introduced in Azure Event Hubs. 使用高级消息传送,峰值性能比使用标准层快得多。With Premium Messaging, peak performance is much faster than with the Standard tier.

高级消息传送技术差异Premium Messaging technical differences

以下部分介绍高级和标准消息传送层之间的一些差异。The following sections discuss a few differences between Premium and Standard messaging tiers.

分区的队列和主题Partitioned queues and topics

高级消息传送不支持分区队列和主题。Partitioned queues and topics are not supported in Premium Messaging. 有关分区的详细信息,请参阅 分区的队列和主题For more information about partitioning, see Partitioned queues and topics.

快速实体Express entities

由于高级消息传送在一个完全隔离的运行时环境中运行,因此高级命名空间中不支持快速实体。Because Premium messaging runs in a completely isolated run-time environment, express entities are not supported in Premium namespaces. 有关快速功能的详细信息,请参阅 QueueDescription.EnableExpress 属性。For more information about the express feature, see the QueueDescription.EnableExpress property.

如果有在标准传送下运行的代码并且希望将其移植到高级层,请确保将 EnableExpress 属性设置为 false(默认值)。If you have code running under Standard messaging and want to port it to the Premium tier, make sure the EnableExpress property is set to false (the default value).

高级消息传送入门Get started with Premium Messaging

高级消息传送很容易入门,其操作过程类似于标准消息传送。Getting started with Premium Messaging is straightforward and the process is similar to that of Standard Messaging. 一开始时,请在 Azure 门户创建命名空间Begin by creating a namespace in the Azure portal. 确保在“定价层”下选择“高级”。Make sure you select Premium under Pricing tier. 单击“查看完整的定价详细信息”以查看有关每个层级的详细信息。Click View full pricing details to see more information about each tier.

create-premium-namespace

也可以使用 Azure 资源管理器模板创建高级命名空间You can also create Premium namespaces using Azure Resource Manager templates.

后续步骤Next steps

若要了解有关服务总线消息传送的详细信息,请参阅以下链接:To learn more about Service Bus Messaging, see the following links: