Skip to content

Commit 20ff650

Browse files
authored
Merge pull request #227063 from kasun04/main
Update Dedicated tier to include self-serve dedicated clusters GA.
2 parents d8249c3 + df8f0e6 commit 20ff650

File tree

2 files changed

+74
-27
lines changed

2 files changed

+74
-27
lines changed

articles/event-hubs/event-hubs-dedicated-overview.md

Lines changed: 69 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -5,44 +5,90 @@ ms.topic: article
55
ms.date: 02/07/2023
66
---
77

8-
# Overview of Azure Event Hubs dedicated tier
8+
# Overview of Azure Event Hubs Dedicated tier
99

10-
Event Hubs clusters offer **single-tenant deployments** for customers with the most demanding streaming needs. This offering has a guaranteed **99.99%** SLA, which is available only in our dedicated pricing tier. An [Event Hubs cluster](event-hubs-dedicated-overview.md) can ingress millions of events per second with guaranteed capacity and subsecond latency. Namespaces and event hubs created within a cluster include all features of the premium offering and more, but without any ingress limits. The dedicated offering also includes the popular [Event Hubs Capture](event-hubs-capture-overview.md) feature at no additional cost, allowing you to automatically batch and log data streams to [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md) or [Azure Data Lake Storage Gen 1](../data-lake-store/data-lake-store-overview.md).
10+
Event Hubs dedicated clusters are designed to meet the needs of most demanding mission-critical event streaming workloads. These clusters provide a high-performance, low-latency, scalable, and reliable event streaming service for your event streaming applications that are based on AMQP(Event Hubs SDK) or Apache Kafka APIs.
1111

12-
Dedicated clusters are provisioned and billed by **capacity units (CUs)**, a pre-allocated amount of CPU and memory resources. You can purchase up to 10 CUs for a cluster in the Azure portal. If you need a cluster larger than 10 CU, you can submit an Azure support request to scale up your cluster after its creation.
12+
## Why Dedicated cluster?
13+
The dedicated tier of Event Hubs offers several benefits to customers who need run mission-critical workloads at enterprise-level capacity.
1314

14-
How much you can ingest and stream per CU depends on various factors, such as the following ones:
15+
### Low latency event streaming
16+
These clusters are optimized for low end-to-end latency and high performance. Therefore these clusters enable businesses to handle high-velocity and high-volume data streaming.
1517

18+
### Streaming large volumes of data
19+
Dedicated clusters can stream events at the gigabytes per second or millions of events per second scale for Most of the use cases. Also, these clusters can be easily scaled to accommodate changes in event streaming volume.
20+
21+
22+
### Guaranteed consistent performance
23+
Event Hubs dedicated clusters minimize the latency jitter and ensure consistent performance with guaranteed capacity.
24+
25+
### Zero interference
26+
Event Hubs Dedicated Clusters operate on a single-tenant architecture. Therefore it ensures that the allocated resources being not shared with any other tenants. Therefore, unlike other tiers, you wouldn't see any cross tenant interference in Dedicated cluster.
27+
28+
### Self-serve scaling
29+
The dedicated cluster offers self-serve scaling capabilities that allow you to adjust the capacity of the cluster according to dynamic loads and to facilitate business operations. You can scale out during spikes in usage and scale in when the usage is low.
30+
31+
### High-end features and generous quotas
32+
Dedicated clusters include all features of the Premium tier and more. The service also manages load balancing, operating system updates, security patches, and partitioning. So, you can spend less time on infrastructure maintenance and more time on building your event streaming applications.
33+
34+
## Capacity Units(CU)
35+
Dedicated clusters are provisioned and billed by capacity units (CUs), a pre-allocated amount of CPU and memory resources.
36+
37+
How much you can ingest and stream per CU depends on various factors, such as the following ones:
1638
- Number of producers and consumers
17-
- Payload shape
39+
- Number of partitions.
40+
- Producer and consumer configuration.
41+
- Payload size
1842
- Egress rate
1943

20-
> [!NOTE]
21-
> All Event Hubs clusters are Kafka-enabled by default and support Kafka endpoints that can be used by your existing Kafka based applications. Having Kafka enabled on your cluster does not affect your non-Kafka use cases. There is no option or need to disable Kafka on a cluster.
44+
Therefore, to determine the necessary number of CUs, you should carry out your anticipated event streaming workload on an Event Hubs dedicated cluster while observing the cluster's resource utilization. For more information, see [When to scale my dedicated cluster](#when-to-scale-my-dedicated-cluster).
2245

23-
## Why dedicated tier?
24-
The dedicated tier of Event Hubs offers three compelling benefits to customers who need enterprise-level capacity:
46+
## Cluster Types
47+
Event Hubs Dedicated Clusters come in two distinct types: Self-serve scalable clusters and Legacy clusters. These two types differ in their support for the number of CUs, the amount of throughput each CU provides, and the regional and zone availability.
2548

26-
### Single-tenancy guarantees capacity for better performance
27-
A dedicated cluster guarantees capacity at full scale. It can ingress up to gigabytes of streaming data with fully durable storage and subsecond latency to accommodate any burst in traffic.
49+
As a dedicated cluster user, you can determine the type of cluster by examining the availability of the capacity scaling feature in the portal. If this capability is present, you're using a self-serve scalable cluster. Conversely, if it isn't available, you're utilizing a legacy dedicated cluster. Alternatively you can look for the [Azure Resource Manager properties](/azure/templates/microsoft.eventhub/clusters?pivots=deployment-language-arm-template) related to Dedicated clusters.
2850

29-
### Inclusive and exclusive access to features
30-
The dedicated offering includes features like [Event Hubs Capture](event-hubs-capture-overview.md) at no additional cost and exclusive access to features like [Bring Your Own Key (BYOK)](configure-customer-managed-key.md). The service also manages load balancing, operating system updates, security patches, and partitioning. So, you can spend less time on infrastructure maintenance and more time on building client-side features.
51+
### Self-serve scalable clusters
52+
Event Hubs Self-serve scalable clusters are based on new infrastructure and allow users to easily scale the number of capacity units allocated to each cluster. By creating a dedicated cluster through the Event Hubs portal or ARM templates, you gain access to a self-service scalable cluster. To learn how to scale your dedicated cluster, see [Scale Event Hubs dedicated clusters](event-hubs-dedicated-cluster-create-portal.md).
3153

32-
### Self-Serve scaling capabilities 
33-
The dedicated tier offers self-serve scaling capabilities that allow you to adjust the capacity of the cluster according to dynamic loads and to facilitate business operations. You can scale out during spikes in usage and scale in when the usage is low. To learn how to scale your dedicated cluster, see [Scale Event Hubs dedicated clusters](event-hubs-dedicated-cluster-create-portal.md).
3454

35-
## Quotas and limits
36-
The Event Hubs dedicated offering is billed at a fixed monthly price, with a **minimum of 4 hours of usage**. The dedicated tier offers all the features of the premium plan, but with enterprise-scale capacity and limits for customers with demanding workloads.
55+
Approximately, one capacity unit (CU) in a self-serve scalable cluster provides *ingress capacity ranging from 100 MB/s to 200 MB/s*, although actual throughput may fluctuate depending on various factors.
3756

38-
For more information about quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md)
57+
With self-serve scalable clusters, you can purchase up to 10 CUs for a cluster in the Azure portal. In contrast to traditional clusters, these clusters can be scaled incrementally with CUs ranging from 1 to 10.
58+
If you need a cluster larger than 10 CU, you can [submit a support request](event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) to scale up your cluster after its creation.
59+
60+
> [!IMPORTANT]
61+
> Self-serve scalable dedicated clusters currently don't support [availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones). If you need to use AZ with your dedicated cluster, then you need to explicitly create a Legacy dedicated cluster.
3962
40-
## High availability with availability zones
41-
Event Hubs standard, premium, and dedicated tiers offer [availability zones](../availability-zones/az-overview.md#availability-zones) support where you can run event streaming workloads in physically separate locations within each Azure region that are tolerant to local failures.
63+
### Legacy clusters
64+
Event Hubs dedicated clusters created prior to the availability of self-serve scalable clusters are referred to as legacy clusters.
65+
66+
To use these legacy clusters, direct creation through the Azure portal or ARM templates isn't possible and you must instead [submit a support request](event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) to create one.
67+
68+
Approximately, one capacity unit (CU) in a self-serve scalable cluster provides *ingress capacity ranging from 50 MB/s to 100 MB/s*, although actual throughput may fluctuate depending on various factors.
69+
70+
With Legacy cluster, you can purchase up to 20 CUs.
71+
72+
> [!Note]
73+
> Event Hubs Dedicated clusters require at least 8 Capacity Units(CUs) to enable availability zones. Clusters with self-serve scaling does not support availability zones yet. Availability zone support is only available in [Azure regions with availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones).
4274
4375
> [!IMPORTANT]
44-
> Event Hubs dedicated clusters require at least 8 Capacity Units(CUs) to enable availability zones. Clusters with self-serve scaling does not support availability zones yet. Availability zone support is only available in [Azure regions with availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones).
76+
> Migrating an existing Legacy cluster to a Self-Serve Cluster isn't currently support. For more information, see [migrating a Legacy cluster to Self-Serve Scalable cluster.](#can-i-migrate-my-standard-or-premium-namespaces-to-a-dedicated-tier-cluster).
77+
78+
## Determining cluster type
79+
80+
You can determine the cluster type that you are using the following methods.
4581

82+
| Method | Action | Self-serve scalable clusters | Legacy clusters | Notes |
83+
| -------------| ------------- | --------- | --------- | --------- |
84+
| Using Portal | Check for presence of ‘Scale’ tab under the cluster | ‘Scale’ page available in the cluster UI.| No scale page available in the cluster UI. | |
85+
| Using Azure Resource Manager| Check for `supportsScaling` Azure Resource Manager property on cluster. | Check for presence of ‘Scale’ page under the cluster.  | No scale page available in the cluster UI. | Check this property on Portal, CLI or PowerShell. Needs API version *2022-01-01-preview* or newer. |
86+
| Using nslookup| Run nslookup command on a namespace in cluster. | CNAME maps to `*.cloudapp.azure.com`| CNAME maps to `*.cloudapp.net`. | Example: `nslookup ns.servicebus.windows.net`. |
87+
88+
## Quotas and limits
89+
The Event Hubs dedicated offering is billed at a fixed monthly price, with a **minimum of 4 hours of usage**. The dedicated tier offers all the features of the premium plan, but with enterprise-scale capacity and limits for customers with demanding workloads.
90+
91+
For more information about quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md)
4692

4793
## How to onboard
4894
Event Hubs dedicated tier is generally available (GA). The self-serve experience to create an Event Hubs cluster through the [Azure portal](event-hubs-dedicated-cluster-create-portal.md) is currently in Preview. You can also request for the cluster to be created by contacting the [Event Hubs team](mailto:[email protected]).
@@ -53,8 +99,8 @@ Event Hubs dedicated tier is generally available (GA). The self-serve experience
5399

54100
## Next steps
55101

56-
Contact your Microsoft sales representative or Microsoft Support to get additional details about Event Hubs Dedicated. You can also create a cluster or learn more about Event Hubs pricing tiers by visiting the following links:
102+
Contact your Microsoft sales representative or Microsoft Support to get more details about Event Hubs Dedicated. You can also create a cluster or learn more about Event Hubs pricing tiers by visiting the following links:
57103

58104
- [Create an Event Hubs cluster through the Azure portal](https://aka.ms/eventhubsclusterquickstart)
59-
- [Event Hubs Dedicated pricing](https://azure.microsoft.com/pricing/details/event-hubs/). You can also contact your Microsoft sales representative or Microsoft Support to get additional details about Event Hubs Dedicated capacity.
105+
- [Event Hubs Dedicated pricing](https://azure.microsoft.com/pricing/details/event-hubs/). You can also contact your Microsoft sales representative or Microsoft Support to get more details about Event Hubs Dedicated capacity.
60106
- The [Event Hubs FAQ](event-hubs-faq.yml) contains pricing information and answers some frequently asked questions about Event Hubs.

articles/event-hubs/includes/event-hubs-dedicated-clusters-faq.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: "include file"
1515

1616
For an Event Hubs cluster, how much you can ingest and stream depends on various factors such as your producers, consumers, the rate at which you're ingesting and processing, and much more.
1717

18-
The following table shows the benchmark results that we achieved during our testing:
18+
The following table shows the benchmark results that we achieved during our testing a Legacy dedicated cluster:
1919

2020
| Payload shape | Receivers | Ingress bandwidth| Ingress messages | Egress bandwidth | Egress messages | Total TUs | TUs per CU |
2121
| ------------- | --------- | ---------------- | ------------------ | ----------------- | ------------------- | --------- | ---------- |
@@ -30,7 +30,7 @@ In the testing, the following criteria were used:
3030
- The data that was ingested was received by two receiver applications receiving from all partitions.
3131

3232
### Can I scale up/down my cluster?
33-
If you created the cluster with the **Support Scaling** option set, you can use the [self-serve experience](../event-hubs-dedicated-cluster-create-portal.md#scale-event-hubs-dedicated-cluster) to scale out and scale in as needed. You can scale up to 10 CUs with self-serve scalable clusters. As self-serve scalable dedicated clusters are based out of new infrastructure, they are bound to be performant over dedicated clusters that don't support self-serve scaling. As the performance of dedicated clusters depends on various factors such as resource allocation, number of partitions, storage, and so on, we recommend you to determine the required number of CUs after testing with a real workload.
33+
If you created the cluster with the **Support Scaling** option set, you can use the [self-serve experience](../event-hubs-dedicated-cluster-create-portal.md#scale-event-hubs-dedicated-cluster) to scale out and scale in as needed. You can scale up to 10 CUs with self-serve scalable clusters. As self-serve scalable dedicated clusters are based out of new infrastructure, they're bound to be performant over dedicated clusters that don't support self-serve scaling. As the performance of dedicated clusters depends on various factors such as resource allocation, number of partitions, storage, and so on, we recommend you to determine the required number of CUs after testing with a real workload.
3434

3535
[Submit a support request](../event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) in the following scenarios to scale out or scale in your dedicated cluster.
3636

@@ -43,8 +43,9 @@ If you created the cluster with the **Support Scaling** option set, you can use
4343
> You won't be able to delete the cluster for at least 4 hours after you create it. Therefore, you will be charged for a minimum 4 hours of usage of the cluster. For more information on pricing, see [Event Hubs - Pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
4444
4545

46-
### Can I migrate from non-scalable cluster to scalable cluster?
47-
Due to difference in the backend architecture, we don't currently support migration of clusters that don't support self-serve scaling to self-serve scalable dedicated clusters. If you would wish to use self-serve scaling, you must recreate the cluster with the support for scaling. To learn how to create scalable cluster, see [Create an Event Hubs dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md).
46+
### Can I migrate from a Legacy cluster to a Self-Serve Scalable cluster?
47+
Due to difference in the underlying hardware and software infrastructure, we don't currently support migration of clusters that don't support self-serve scaling to self-serve scalable dedicated clusters. If you would wish to use self-serve scaling, you must recreate the cluster. To learn how to create scalable cluster, see [Create an Event Hubs dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md).
48+
4849

4950

5051
### When to scale my dedicated cluster?

0 commit comments

Comments
 (0)