Skip to content

Commit 58f9634

Browse files
committed
removed sharding section from scaling topic per reza and GH issue
1 parent c32304d commit 58f9634

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/iot-hub/iot-hub-scaling.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,6 @@ For specific burst performance numbers, see [IoT Hub quotas and throttles](iot-h
123123

124124
If you are approaching the allowed message limit on your IoT Hub, you can use these [steps to automatically scale](https://azure.microsoft.com/resources/samples/iot-hub-dotnet-autoscale/) to increment an IoT Hub unit in the same IoT Hub tier.
125125

126-
## Sharding
127-
128-
While a single IoT hub can scale to millions of devices, sometimes your solution requires specific performance characteristics that a single IoT hub cannot guarantee. In that case, you can partition your devices across multiple IoT hubs. Multiple IoT hubs smooth traffic bursts and obtain the required throughput or operation rates that are required.
129-
130126
## Next steps
131127

132128
* For more information about IoT Hub capabilities and performance details, see [IoT Hub pricing](https://azure.microsoft.com/pricing/details/iot-hub) or [IoT Hub quotas and throttles](iot-hub-devguide-quotas-throttling.md).

0 commit comments

Comments
 (0)