You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-premium-overview.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
title: Overview of Event Hubs Premium
3
-
description: This article provides an overview of Azure Event Hubs Premium, which offers multi-tenant deployments of Event Hubs for high-end streaming needs.
3
+
description: This article provides an overview of Azure Event Hubs Premium, which offers multitenant deployments of Event Hubs for high-end streaming needs.
4
4
ms.topic: article
5
-
ms.date: 09/20/2022
5
+
ms.date: 02/15/2024
6
6
---
7
7
8
8
# Overview of Event Hubs Premium
9
-
The Event Hubs Premium (premium tier) is designed for high-end streaming scenarios that require elastic, superior performance with predictable latency. The performance is achieved by providing reserved compute, memory, and storage resources, which minimize cross-tenant interference in a managed multi-tenant PaaS environment.
9
+
The Event Hubs Premium (premium tier) is designed for high-end streaming scenarios that require elastic, superior performance with predictable latency. The premium tier provides reserved compute, memory, and storage resources, which minimize cross-tenant interference in a managed multitenant PaaS environment.
10
10
11
11
It replicates events to three replicas, distributed across Azure availability zones where available. All replicas are synchronously flushed to the underlying fast storage before the send operation is reported as completed. Events that aren't read immediately or that need to be re-read later can be retained up to 90 days, transparently held in an availability-zone redundant storage tier.
12
12
@@ -17,7 +17,7 @@ In addition to these storage-related features and all capabilities and protocol
17
17
> - The premium tier isn't available in all regions. Try to create a namespace in the Azure portal and see supported regions in the **Location** drop-down list on the **Create Namespace** page.
18
18
19
19
20
-
You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
20
+
You can purchase 1, 2, 4, 8 and 16 processing units (PU) for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU depends on various factors, including:
21
21
22
22
* Number of producers and consumers
23
23
* Payload size
@@ -34,23 +34,23 @@ The premium tier offers three compelling benefits for customers who require bett
34
34
The premium tier uses a new two-tier log storage engine that drastically improves the data ingress performance with substantially reduced overall latency without compromising the durability guarantees.
35
35
36
36
### Better isolation and predictability
37
-
The premium tier offers an isolated compute and memory capacity to achieve more predictable latency and far reduced *noisy neighbor* impact risk in a multi-tenant deployment.
37
+
The premium tier offers an isolated compute and memory capacity to achieve more predictable latency and far reduced *noisy neighbor* impact risk in a multitenant deployment.
38
38
39
39
It implements a *cluster in cluster* model in its multitenant clusters to provide predictability and performance while retaining all the benefits of a managed multitenant PaaS environment.
40
40
41
41
### Cost savings and scalability
42
-
As the premium tier is a multitenant offering, it can dynamically scale more flexibly and very quickly. Capacity is allocated in processing units (PUs) that allocate isolated pods of CPU/memory inside the cluster. The number of those pods can be scaled up/down per namespace. Therefore, the premium tier is a low-cost option for messaging scenarios with the overall throughput range that is less than 120 MB/s but higher than what you can achieve with the standard SKU.
42
+
As the premium tier is a multitenant offering, it can dynamically scale more flexibly and very quickly. Capacity is allocated in processing units (PUs) that allocate isolated pods of CPU and memory inside the cluster. The number of those pods can be scaled up or down per namespace. Therefore, the premium tier is a low-cost option for messaging scenarios with the overall throughput range that is less than 120 MB/s but higher than what you can achieve with the standard tier.
43
43
44
44
## Encryption of events
45
-
Azure Event Hubs provides encryption of data at rest with Azure Storage Service Encryption (Azure SSE). The Event Hubs service uses Azure Storage to store the data. All the data that's stored with Azure Storage is encrypted using Microsoft-managed keys. If you use your own key (also referred to as Bring Your Own Key (BYOK) or customer-managed key), the data is still encrypted using the Microsoft-managed key, but in addition the Microsoft-managed key will be encrypted using the customer-managed key. This feature enables you to create, rotate, disable, and revoke access to customer-managed keys that are used for encrypting Microsoft-managed keys. Enabling the BYOK feature is a one time setup process on your namespace. For more information, see [Configure customer-managed keys for encrypting Azure Event Hubs data at rest](configure-customer-managed-key.md).
45
+
Azure Event Hubs provides encryption of data at rest with Azure Storage Service Encryption (Azure SSE). The Event Hubs service uses Azure Storage to store the data. All the data that's stored with Azure Storage is encrypted using Microsoft-managed keys. If you use your own key (also referred to as Bring Your Own Key (BYOK) or customer-managed key), the data is still encrypted using the Microsoft-managed key, but in addition the Microsoft-managed key is encrypted using the customer-managed key. This feature enables you to create, rotate, disable, and revoke access to customer-managed keys that are used for encrypting Microsoft-managed keys. Enabling the BYOK feature is a one time setup process on your namespace. For more information, see [Configure customer-managed keys for encrypting Azure Event Hubs data at rest](configure-customer-managed-key.md).
46
46
47
47
> [!NOTE]
48
48
> All Event Hubs namespaces are enabled for the Apache Kafka RPC protocol by default 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.
49
49
50
50
51
51
## Quotas and limits
52
52
The premium tier offers all the features of the standard plan, but with better performance, isolation and more generous quotas.
53
-
For more quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md)
53
+
For more quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md).
54
54
55
55
## High availability with availability zones
56
56
Event Hubs standard, premium, and dedicated tiers offer [availability zones](../availability-zones/az-overview.md#availability-zones) support with no extra cost. Using availability zones, you can run event streaming workloads in physically separate locations within each Azure region that are tolerant to local failures.
description: Provides frequently asked questions (FAQ) and their answers about Event Hubs Premium.
4
4
author: spelluru
5
5
ms.service: event-hubs
6
6
ms.topic: include
7
-
ms.date: 05/12/2021
7
+
ms.date: 02/15/2024
8
8
ms.author: spelluru
9
9
ms.custom: "include file"
10
10
11
11
---
12
12
13
-
### What can I achieve with a Processing Unit?
13
+
### What can I achieve with a processing unit (PU)?
14
14
15
-
How much you can ingest and stream with a Processing Unit depends on various factors such as your producers, consumers, the rate at which you're ingesting and processing, and much more.
16
-
Please refer to [Scaling with Event Hubs](../event-hubs-scalability.md) more details on Processing Units.
15
+
How much you can ingest and stream with a PU depends on various factors such as your producers, consumers, the rate at which you're ingesting and processing, and much more. For details on processing units, see [Scaling with Event Hubs](../event-hubs-scalability.md).
17
16
18
-
### Can I migrate my Standard namespaces to Premium namespace?
17
+
### Can I migrate my standard namespaces to a premium namespace?
19
18
We currently don't support migrating from standard namespaces to premium namespace.
The following table shows limits that may be different for basic, standard, premium, and dedicated tiers.
13
+
The following table shows limits that are different for basic, standard, premium, and dedicated tiers.
14
14
15
15
> [!NOTE]
16
16
> - In the table, CU is [capacity unit](../event-hubs-dedicated-overview.md), PU is [processing unit](../event-hubs-scalability.md#processing-units), and TU is [throughput unit](../event-hubs-scalability.md#throughput-units).
@@ -20,7 +20,7 @@ The following table shows limits that may be different for basic, standard, prem
| Maximum size of Event Hubs publication | 256 KB | 1 MB | 1 MB | 1 MB |
23
-
| Number of Event Hub consumer groups per event hub | 1 | 20 | 100 | 1000<br/>No limit per CU |
23
+
| Number of consumer groups per event hub | 1 | 20 | 100 | 1000<br/>No limit per CU |
24
24
| Number of Kafka consumer groups per Namespace | NA | 1000 | 1000 | 1000 |
25
25
| Number of brokered connections per namespace | 100 | 5,000 | 10000 per PU<br/><br/>For example, if the namespace is assigned 3 PUs, the limit is 30000. | 100, 000 per CU |
26
26
| Maximum retention period of event data | 1 day | 7 days | 90 days | 90 days |
@@ -33,7 +33,7 @@ The following table shows limits that may be different for basic, standard, prem
33
33
| Size of the schema registry (namespace) in mega bytes | N/A | 25 | 100 | 1024 |
34
34
| Number of schema groups in a schema registry or namespace | N/A | 1 - excluding the default group | 100 <br/>1 MB per schema | 1000<br/>1 MB per schema |
35
35
| Number of schema versions across all schema groups | N/A | 25 | 1000 | 10000 |
36
-
| Throughput per unit | Ingress - 1 MB/s or 1000 events per second<br/>Egress – 2 MB/s or 4096 events per second | Ingress - 1 MB/s or 1000 events per second<br/>Egress – 2 MB/s or 4096 events per second | No limits per PU * | No limits per CU * |
36
+
| Throughput per unit | Ingress - 1 MB/s or 1000 events per second<br/>Egress – 2 MB/s or 4,096 events per second | Ingress - 1 MB/s or 1000 events per second<br/>Egress – 2 MB/s or 4,096 events per second | No limits per PU * | No limits per CU * |
37
37
38
38
\* Depends on various factors such as resource allocation, number of partitions, storage, and so on.
0 commit comments