Announcing public preview of performance improving features for Azure Service Bus Premium

Posted by

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Today we are pleased to announce that you will be able to enable much higher throughput levels for Azure Service Bus Premium. This is accomplished through two new features we are releasing in public preview. They will be available in East US and South-Central US soon, around Ignite timeframe, with more regions following.

 

First, we are releasing scaling partitions, which allows the use of partitioning for the premium messaging tier in public preview. This means that the overall throughput of a partitioned entity is no longer limited by the performance of a single message broker. Additionally, a temporary outage of a message broker, for example during an upgrade, doesn't render a partitioned queue or topic unavailable, as messages will be retried on a different partition.

 

Second, we are making a change to our infrastructure, which will result in more consistent low latency. This is accomplished by switching our storage infrastructure to a different implementation called Local Store. During public preview we will create partitioned namespaces using this new feature, but in the future all new namespaces will be created on Local Store.

 

Partitioning

Scaling partitions in premium namespaces work in close conjunction with scaling through Messaging Units, as the configured MUs on a namespace are equally distributed across the different partitions. Currently it is possible to scale up to 4 partitions, meaning we can scale up to a total of 64MU.

 

There are some differences between partitioning in the standard and premium SKUs. First, the number of partitions can be configured during namespace creation on the premium SKU, while partitioned namespaces in the standard SKU comes with a fixed number of partitions. Second, unlike the standard SKU, partitioned namespaces in the premium SKU do not allow non-partitioned entities in them.

 

Additionally, there are some limitations which may be encountered during public preview, which will be resolved before going into GA. The first limitation is that it is not possible to use JMS on partitioned entities. The second limitation is around metrics, which are currently only available on an aggregated namespace level, not for individual partitions.

 

To enable partitions, select the number of partitions during creation of a new namespace. Please note that it is not possible to change the number of partitions after creation. More details can be found in the documentation.

 

 

EldertGrootenboer_0-1664490652226.png

 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.