Merge pull request #186023 from spelluru/patch-77

Removed client-side batching section

Author: PRMerger6

articles/service-bus-messaging/advanced-features-overview.md

@@ -2,7 +2,7 @@
 title: Azure Service Bus messaging - advanced features
 description: This article provides a high-level overview of advanced features in Azure Service Bus. 
 ms.topic: overview
-ms.date: 06/11/2021
+ms.date: 01/24/2022
 ---
 
 # Azure Service Bus - advanced features
@@ -29,9 +29,6 @@ You can submit messages to a queue or a topic for delayed processing, setting a
 ## Message deferral
 A queue or subscription client can defer retrieval of a received message until a later time. The message may have been posted out of an expected order and the client wants to wait until it receives another message. Deferred messages remain in the queue or subscription and must be reactivated explicitly using their service-assigned sequence number. For more information, see [Message deferral](message-deferral.md).
 
-## Batching
-Client-side batching enables a queue or topic client to accumulate a set of messages and transfer them together. It's often done to either save bandwidth or to increase throughput. For more information, see [Client-side batching](service-bus-performance-improvements.md#client-side-batching).
-
 ## Transactions
 A transaction groups two or more operations together into an execution scope. Service Bus allows you to group operations against multiple messaging entities within the scope of a single transaction. A message entity can be a queue, topic, or subscription. For more information, see [Overview of Service Bus transaction processing](service-bus-transactions.md).
 

articles/service-bus-messaging/service-bus-messaging-overview.md

@@ -2,7 +2,7 @@
 title: Azure Service Bus messaging overview | Microsoft Docs
 description: This article provides a high-level overview of Azure Service Bus, a fully managed enterprise integration message broker. It also explains concepts such as namespaces, queues, and topics in Service Bus. 
 ms.topic: overview
-ms.date: 11/11/2021
+ms.date: 01/24/2022
 ms.custom: contperf-fy22q2
 ---
 
@@ -103,10 +103,6 @@ You can submit messages to a queue or topic [for delayed processing](message-seq
 
 When a queue or subscription client receives a message that it's willing to process, but for which processing isn't currently possible because of special circumstances within the application, the entity can [defer retrieval of the message](message-deferral.md) to a later point. The message remains in the queue or subscription, but it's set aside.
 
-### Batching
-
-[Client-side batching](service-bus-performance-improvements.md#client-side-batching) enables a queue or topic client to delay sending a message for a certain period of time. If the client sends more messages during this time period, it transmits the messages in a single batch. 
-
 ### Transactions
 
 A [transaction](service-bus-transactions.md) groups two or more operations together into an execution scope. Service Bus supports grouping operations against a single messaging entity (queue, topic, subscription) within the scope of a transaction.
@@ -177,4 +173,4 @@ To get started using Service Bus messaging, see the following articles:
 - [Service Bus queues, topics, and subscriptions](service-bus-queues-topics-subscriptions.md)
 - Quickstarts: [.NET](service-bus-dotnet-get-started-with-queues.md), [Java](service-bus-java-how-to-use-queues.md), or [JMS](service-bus-java-how-to-use-jms-api-amqp.md).
 - [Service Bus pricing](https://azure.microsoft.com/pricing/details/service-bus/). 
-- [Premium Messaging](service-bus-premium-messaging.md).
+- [Premium Messaging](service-bus-premium-messaging.md).

articles/service-bus-messaging/service-bus-performance-improvements.md

@@ -2,7 +2,7 @@
 title: Best practices for improving performance using Azure Service Bus
 description: Describes how to use Service Bus to optimize performance when exchanging brokered messages.
 ms.topic: article
-ms.date: 08/30/2021
+ms.date: 01/24/2021
 ms.devlang: csharp
 ---
 
@@ -279,47 +279,6 @@ When setting the receive mode to `ReceiveAndDelete`, both steps are combined in
 
 Service Bus doesn't support transactions for receive-and-delete operations. Also, peek-lock semantics are required for any scenarios in which the client wants to defer or [dead-letter](service-bus-dead-letter-queues.md) a message.
 
-## Client-side batching
-
-Client-side batching enables a queue or topic client to delay the sending of a message for a certain period of time. If the client sends additional messages during this time period, it transmits the messages in a single batch. Client-side batching also causes a queue or subscription client to batch multiple **Complete** requests into a single request. Batching is only available for asynchronous **Send** and **Complete** operations. Synchronous operations are immediately sent to the Service Bus service. Batching doesn't occur for peek or receive operations, nor does batching occur across clients.
-
-# [Azure.Messaging.ServiceBus SDK](#tab/net-standard-sdk-2)
-Batching functionality for the .NET Standard SDK doesn't yet expose a property to manipulate.
-
-# [Microsoft.Azure.ServiceBus SDK](#tab/net-standard-sdk)
-
-Batching functionality for the .NET Standard SDK doesn't yet expose a property to manipulate.
-
-# [WindowsAzure.ServiceBus SDK](#tab/net-framework-sdk)
-
-By default, a client uses a batch interval of 20 ms. You can change the batch interval by setting the [BatchFlushInterval][BatchFlushInterval] property before creating the messaging factory. This setting affects all clients that are created by this factory.
-
-To disable batching, set the [BatchFlushInterval][BatchFlushInterval] property to **TimeSpan.Zero**. For example:
-
-```csharp
-var settings = new MessagingFactorySettings
-{
-    NetMessagingTransportSettings =
-    {
-        BatchFlushInterval = TimeSpan.Zero
-    }
-};
-var factory = MessagingFactory.Create(namespaceUri, settings);
-```
-
-Batching doesn't affect the number of billable messaging operations, and is available only for the Service Bus client protocol using the [Microsoft.ServiceBus.Messaging](https://www.nuget.org/packages/WindowsAzure.ServiceBus/) library. The HTTP protocol doesn't support batching.
-
-> [!NOTE]
-> Setting `BatchFlushInterval` ensures that the batching is implicit from the application's perspective. i.e.; the application makes `SendAsync` and `CompleteAsync` calls and doesn't make specific Batch calls.
->
-> Explicit client side batching can be implemented by utilizing the below method call:
-> ```csharp
-> Task SendBatchAsync(IEnumerable<BrokeredMessage> messages);
-> ```
-> Here the combined size of the messages must be less than the maximum size supported by the pricing tier.
-
----
-
 ## Batching store access
 
 To increase the throughput of a queue, topic, or subscription, Service Bus batches multiple messages when it writes to its internal store.