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
description: This article compares supported tiers of Azure Event Hubs.
3
+
description: This article compares supported tiers of Azure Event Hubs.
4
4
ms.topic: article
5
5
ms.date: 02/15/2024
6
6
---
7
7
8
-
# Compare Azure Event Hubs tiers
8
+
# Compare Azure Event Hubs tiers
9
+
9
10
This article compares tiers of Azure Event Hubs.
10
11
11
12
> [!NOTE]
12
-
> This article compares only features and quotas of tiers. For pricing information, see [Azure Event Hubs pricing](https://azure.microsoft.com/pricing/details/event-hubs/)
13
+
> This article compares only features and quotas of tiers. For pricing information, see [Azure Event Hubs pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
title: Azure Quickstart - Send and receive large messages with Azure Event Hubs (Preview)
2
+
title: 'Quickstart: Send and receive large messages with Azure Event Hubs (preview)'
3
3
description: In this quickstart, you learn how to send and receive large messages with Azure Event Hubs.
4
4
ms.topic: quickstart
5
5
ms.author: Saglodha
6
6
ms.date: 5/6/2024
7
7
---
8
8
9
-
# QuickStart: Send and receive large messages with Azure Event Hubs (Preview)
9
+
# Quickstart: Send and receive large messages with Azure Event Hubs (preview)
10
10
11
-
In this quickstart, you learn how to send and receive large messages (up to 20 MB) using Azure Event Hubs. If you're new to Azure Event Hubs, see[Event Hubs overview](event-hubs-about.md) before you go through this quickstart.
11
+
In this quickstart, you learn how to send and receive large messages (up to 20 MB) by using Azure Event Hubs. If you're new to Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you go through this quickstart.
12
12
13
13
### Prerequisites
14
14
15
-
To complete this QuickStart, you need the following prerequisites:
15
+
To complete this quickstart, you need the following prerequisites:
16
16
17
-
- Microsoft Azure subscription. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or use your MSDN subscriber benefits when you [create an account](https://azure.microsoft.com/).
18
-
19
-
- Create [Self-serve scalable dedicated cluster](event-hubs-dedicated-cluster-create-portal.md), event hubs namespace and an event hub. The first step is to use the Azure portal to create a Dedicated cluster and namespace inside a cluster. To create an event hub, see [QuickStart: Create an event hub using Azure portal. ](event-hubs-create.md). You can skip this step if you already have a self-serve scalable dedicated cluster.
17
+
- An Azure subscription. To use Azure services, including Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or use your MSDN subscriber benefits when you [create an account](https://azure.microsoft.com/).
18
+
- A [self-serve scalable dedicated cluster](event-hubs-dedicated-cluster-create-portal.md), an event hubs namespace, and an event hub. The first step to meet this prerequisite is to use the Azure portal to create a dedicated cluster and namespace inside a cluster. To create an event hub, see [Quickstart: Create an event hub by using the Azure portal](event-hubs-create.md). You can skip this step if you already have a self-serve scalable dedicated cluster.
20
19
21
20
> [!NOTE]
22
-
> Large Message Support, currently in Public Preview, is exclusively available with certain Event Hubs self-serve dedicated clusters. Streaming large messages with these clusters incurs no extra charges.
21
+
> Large message support, currently in public preview, is exclusively available with certain Event Hubs self-serve dedicated clusters. Streaming large messages with these clusters incurs no extra charges.
22
+
23
+
## Configure an Event Hubs dedicated cluster
23
24
24
-
## Configuring Event Hubs Dedicated Cluster
25
+
To stream large messages, you must configure your self-serve scalable dedicated cluster.
25
26
26
-
To stream large messages, you must configure your self-serve scalable dedicated cluster. You could follow below steps below:
27
+
In the Azure portal, go to the **Settings** section for the dedicated cluster. Under **Settings**, select the **Quota** tab.
27
28
28
-
- On Azure portal, navigate to the ‘Settings’ section for Dedicated cluster and select the ‘Quota’ tab under Settings.
29
-
30
-
:::image type="content" source="./media/event-hubs-quickstart-stream-large-messages/large-message-configuration-for-dedicated-cluster.png" alt-text="Screenshot showing the Quota blade for Dedicated Cluster.":::
29
+
:::image type="content" source="./media/event-hubs-quickstart-stream-large-messages/large-message-configuration-for-dedicated-cluster.png" alt-text="Screenshot that shows the Quota pane for a dedicated cluster.":::
31
30
32
-
- Validate that the value for read-only key **supportslargemessages** is set to true.
33
-
- You could update the key: **eventhubmaxmessagesizeinbytes** to suitable value in bytes. Acceptable range for this value is between 1048576 and 20971520 bytes.
31
+
- Validate that the value for the read-only key `supportslargemessages` is set to `True`.
32
+
- You can update the key`eventhubmaxmessagesizeinbytes` to a suitable value in bytes. An acceptable range for this value is between 1,048,576 and 20,971,520 bytes.
34
33
35
-
Once the configuration is saved, you're all set to stream Large messages with event hubs.
34
+
After the configuration is saved, you're ready to stream large messages with Event Hubs.
36
35
37
36
> [!IMPORTANT]
38
-
> Large message streaming is only supported with Self-serve scalable dedicated clusters built out of latest infrastructure. This capability is reflected by the “Supportslargemessages” key.
39
-
> If its value is false, the cluster will not support large message streaming. To enable this feature, you must recreate the cluster.
37
+
> Large message streaming is only supported with self-serve scalable dedicated clusters built out of the latest infrastructure. This capability is reflected by the `Supportslargemessages` key.
38
+
>
39
+
> If a cluster value is false, it won't support large message streaming. To enable this feature, you must re-create the cluster.
40
40
41
-
## Streaming Large messages with Azure Event hubs
41
+
## Stream large messages with Event Hubs
42
42
43
-
Azure Event Hubs allows streaming of large messages up to 20 MB, both in batches and as individual publications. Being able to stream large messages or events requires no client code changes apart from the change in message or event itself. You could continue sending/receiving messages using any existing event hubs SDK/ Kafka API to stream large messages to event hub. This allows you to stream large messages to the event hub in the same manner as you would for messages of size less than 1 MB.
44
-
Know more [here](event-hubs-dotnet-standard-getstarted-send.md)
43
+
Event Hubs allows streaming of large messages up to 20 MB, both in batches and as individual publications. The ability to stream large messages or events requires no client code changes apart from the change in the message or event itself. You can continue sending or receiving messages by using any existing Event Hubs SDK or Kafka API to stream large messages to Event Hubs. This way you can stream large messages to Event Hubs in the same manner as you would for messages of sizes less than 1 MB.
45
44
45
+
For more information, see [Send events to and receive events from Event Hubs by using .NET](event-hubs-dotnet-standard-getstarted-send.md).
46
46
47
47
> [!TIP]
48
-
> Make sure to review any Event Hubs AMQP client or Kafka client configuration that could be limiting maximum message size that you stream into event hubs.You must update Client timeout to higher value to be able to stream large messages. By default, AMQP client prefetch count is 300. You should lower this value to avoid client side memory issues when dealing with large messages.
49
-
50
-
For complete .NET library reference, see our [SDK documentation](/dotnet/api/overview/azure/event-hubs).
48
+
> Make sure to review any Event Hubs Advanced Message Queuing Protocol (AMQP) client or Kafka client configuration that might limit the maximum message size that you stream into Event Hubs. You must update client timeout to a higher value to stream large messages.
49
+
>
50
+
>By default, the AMQP client prefetch count is 300. Lower this value to avoid client-side memory issues when you deal with large messages.
51
51
52
+
For the complete .NET library reference, see the [SDK documentation](/dotnet/api/overview/azure/event-hubs).
The following table shows limits that are 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
-
> - 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).
17
-
> - You can configure [TUs](../event-hubs-auto-inflate.md#use-azure-portal) for a basic or standard tier namespace or [PUs](../configure-processing-units-premium-namespace.md) for a premium tier namespace.
18
-
> - When you [create a dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md#create-an-event-hubs-dedicated-cluster), 1 CU is assigned to the cluster. If you enable the **Support Scaling** option while creating the cluster, you'll be able to scale out by increasing CUs or scale in by decreasing CUs for the cluster yourself. For step-by-step instructions, see [Scale dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md#scale-a-dedicated-cluster). For clusters that don't support the **Support Scaling** feature, [submit a ticket](../event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request)To adjust CUs for the cluster.
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).
17
+
> - You can configure [TUs](../event-hubs-auto-inflate.md#use-azure-portal) for a Basic or Standard tier namespace or [PUs](../configure-processing-units-premium-namespace.md) for a Premium tier namespace.
18
+
> - When you [create a dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md#create-an-event-hubs-dedicated-cluster), one CU is assigned to the cluster. If you enable the **Support scaling** option while you create the cluster, you can scale out by increasing CUs or scale in by decreasing CUs for the cluster yourself. For step-by-step instructions, see [Scale dedicated cluster](../event-hubs-dedicated-cluster-create-portal.md#scale-a-dedicated-cluster). For clusters that don't support the **Support scaling** feature, [submit a ticket](../event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request)to adjust CUs for the cluster.
| Maximum size of Event Hubs publication | 256 KB | 1 MB | 1 MB |1 MB |
23
-
| Number of consumer groups per event hub | 1 | 20 | 100 |1000<br/>No limit per CU|
24
-
| Number of Kafka consumer groups per Namespace| NA |1000|1000|1000 |
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 |
22
+
| Maximum size of Event Hubs publication | 256 KB | 1 MB | 1 MB | 1 MB |
23
+
| Number of consumer groups per event hub | 1 | 20 | 100 |1,000<br/>No limit per CU |
24
+
| Number of Kafka consumer groups per namespace| NA |1,000|1,000|1,000|
25
+
| Number of brokered connections per namespace | 100 | 5,000 |10,000 per PU<br/><br/>For example, if the namespace is assigned 3 PUs, the limit is 30,000. | 100,000 per CU |
26
26
| Maximum retention period of event data | 1 day | 7 days | 90 days | 90 days |
27
-
| Event storage for retention | 84 GB per TU | 84 GB per TU | 1 TB per PU | 10 TB per CU |
27
+
| Event storage for retention | 84 GB per TU | 84 GB per TU | 1 TB per PU | 10 TB per CU |
28
28
| Maximum TUs or PUs or CUs | 40 TUs | 40 TUs | 16 PUs | 20 CUs |
29
-
| Number of partitions per event hub | 32 | 32 | 100 per event hub, but there's a limit of 200 per PU at the namespace level.<br/><br/> For example, if a namespace is assigned 2 PUs, the limit for total number of partitions in all event hubs in the namespace is 2 * 200 = 400. |1024 per event hub<br/> 2000 per CU |
30
-
| Number of namespaces per subscription |1000|1000|1000|1000 (50 per CU) |
31
-
| Number of event hubs per namespace | 10 | 10 | 100 per PU |1000|
29
+
| Number of partitions per event hub | 32 | 32 | 100 per event hub, but there's a limit of 200 per PU at the namespace level.<br/><br/> For example, if a namespace is assigned 2 PUs, the limit for total number of partitions in all event hubs in the namespace is 2 * 200 = 400. |1,024 per event hub<br/> 2,000 per CU |
30
+
| Number of namespaces per subscription |1,000|1,000|1,000|1,000 (50 per CU) |
31
+
| Number of event hubs per namespace | 10 | 10 | 100 per PU |1,000|
32
32
| Capture | N/A | Pay per hour | Included | Included |
33
-
| Size of compacted event hub | N/A | 1 GB per partition | 250 GB per partition | 250 GB per partition |
34
-
| Size of the schema registry (namespace) in mega bytes | N/A | 25 | 100 |1024|
35
-
| 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 |
36
-
| Number of schema versions across all schema groups | N/A | 25 |1000|10000|
37
-
| 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 * |
33
+
| Size of compacted event hub | N/A | 1 GB per partition | 250 GB per partition | 250 GB per partition |
34
+
| Size of the schema registry (namespace) in megabytes | N/A | 25 | 100 |1,024|
35
+
| Number of schema groups in a schema registry or namespace | N/A | 1: excluding the default group | 100 <br/>1 MB per schema |1,000<br/>1 MB per schema |
36
+
| Number of schema versions across all schema groups | N/A | 25 |1,000|10,000|
37
+
| Throughput per unit | Ingress: 1 MB/sec or 1000 events per second<br/>Egress: 2 MB/sec or 4,096 events per second | Ingress: 1 MB/sec or 1,000 events per second<br/>Egress: 2 MB/sec or 4,096 events per second | No limits per PU * | No limits per CU * |
38
38
39
-
\* Depends on various factors such as resource allocation, number of partitions, storage, and so on.
40
-
39
+
\* Depends on factors such as resource allocation, number of partitions, and storage.
41
40
42
41
> [!NOTE]
43
-
> You can publish events individually or batched.
44
-
> The publication limit (according to SKU) applies regardless of whether it is a single event or a batch. Publishing events larger than the maximum threshold will be rejected.
42
+
> You can publish events individually or batched. The publication limit (according to SKU) applies regardless of whether it's a single event or a batch. Publishing events larger than the maximum threshold will be rejected.
0 commit comments