Merge pull request #265270 from Saglodha/saglodha-LMS

Adding content for Upcoming feature - Large Message Support

Author: ShannonLeavitt

articles/event-hubs/TOC.yml

@@ -58,6 +58,8 @@
         - name: Send events using Data Generator
           href: send-and-receive-events-using-data-generator.md
           displayName: No Code, Sample data
+        - name: Stream large messages
+          href: event-hubs-quickstart-stream-large-messages.md
     - name: Capture events
       items:
         - name: Use the Azure portal to enable Event Hubs Capture

articles/event-hubs/event-hubs-about.md

@@ -70,6 +70,10 @@ You can experience flexible and cost-efficient event streaming through Event Hub
 ### Scalable
 With Event Hubs, you can start with data streams in megabytes, and grow to gigabytes or terabytes. The [Auto inflate](event-hubs-auto-inflate.md) feature is one of the many options available to scale the number of throughput units or processing units to meet your usage needs.
 
+### Supports streaming large messages 
+
+In most streaming scenarios, data is characterized by being lightweight, typically less than 1 MB, and having a high throughput. However, there are instances where messages cannot be divided into smaller segments. Azure Event Hubs can effortlessly accommodate events up to 20 MB with self-serve scalable [dedicated clusters](event-hubs-dedicated-overview.md)at no extra charge. This capability allows Event Hubs to handle a wide range of message sizes, thereby ensuring uninterrupted business operations. For more information, refer stream [large messages](event-hubs-quickstart-stream-large-messages.md).
+
 ### Capture streaming data for long term retention and batch analytics
 Capture your data in near-real time in an Azure Blob storage or Azure Data Lake Storage for long-term retention or micro-batch processing. You can achieve this behavior on the same stream you use for deriving real-time analytics. Setting up capture of event data is fast.  
 

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

@@ -34,6 +34,9 @@ The Dedicated cluster offers self-serve scaling capabilities that allow you to a
 ### High-end features and generous quotas
 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.  
 
+### Supports streaming large messages
+In most streaming scenarios, data is lightweight, typically less than 1 MB, and requires high throughput. However, there are instances where messages cannot be divided into smaller segments. Self-serve Dedicated clusters can effortlessly accommodate events up to 20 MB of size at no additional cost. This capability allows Event Hubs to handle a wide range of message sizes, thereby ensuring uninterrupted business operations. For more information, refer stream [large messages](event-hubs-quickstart-stream-large-messages.md).
+
 ## Capacity Units(CU)
 Dedicated clusters are provisioned and billed by capacity units (CUs), a pre-allocated amount of CPU and memory resources. 
 

articles/event-hubs/event-hubs-quickstart-stream-large-messages.md

@@ -0,0 +1,51 @@
+---
+title: Azure Quickstart - Send and receive large messages with Azure Event Hubs (Preview)
+description: In this quickstart, you learn how to send and receive large messages with Azure Event Hubs.
+ms.topic: quickstart
+ms.author: Saglodha
+ms.date: 5/6/2024
+---
+
+# QuickStart: Send and receive large messages with Azure Event Hubs (Preview)
+
+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.
+
+### Prerequisites
+
+To complete this QuickStart, you need the following prerequisites: 
+
+- 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/). 
+
+- 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.
+
+> [!NOTE]
+> 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.
+
+## Configuring Event Hubs Dedicated Cluster
+
+To stream large messages, you must configure your self-serve scalable dedicated cluster. You could follow below steps below:
+
+- On Azure portal, navigate to the ‘Settings’ section for Dedicated cluster and select the ‘Quota’ tab under Settings.
+  
+:::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.":::
+
+- Validate that the value for read-only key **supportslargemessages** is set to true. 
+- You could update the key: **eventhubmaxmessagesizeinbytes** to suitable value in bytes. Acceptable range for this value is between 1048576 and 20971520 bytes.
+
+Once the configuration is saved, you're all set to stream Large messages with event hubs.
+
+> [!IMPORTANT]
+> 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.
+> If its value is false, the cluster will not support large message streaming. To enable this feature, you must recreate the cluster.
+
+## Streaming Large messages with Azure Event hubs
+
+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. 
+Know more [here](event-hubs-dotnet-standard-getstarted-send.md)
+
+
+> [!TIP]
+> 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.    
+
+For complete .NET library reference, see our [SDK documentation](/dotnet/api/overview/azure/event-hubs). 
+