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/iot/iot-overview-scalability-high-availability.md
+17-2Lines changed: 17 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,13 @@ The following diagram shows a high-level view of the components in a typical clo
32
32
33
33
## IoT solution scalability
34
34
35
-
An IoT solution might need to support millions of connected devices. You need to ensure that the components in your solution can scale to meet the demands.
35
+
An IoT solution might need to support millions of connected assets and devices. You need to ensure that the components in your solution can scale to meet the demands.
36
+
37
+
# [Edge-based solution](#tab/edge)
38
+
39
+
Deploy Azure IoT Operations on a multi-node cluster to ensure that you can handle increased traffic or workload demands. When Azure IoT Operations runs on a multi-node cluster, it can process more data and take advantage of the high-availability capabilities of Kubernetes. The MQTT Broker does automatically replicates states across multiple nodes governed by the Broker's *cardinality* setting. Replicas are distributed across different nodes in a multi-node cluster and data isn't lost if there's one set of replicas running and healthy. To learn more, see [Configure broker settings for high availability, scaling, and memory usage](../manage-mqtt-broker/howto-configure-availability-scale.md#configure-cardinality-directly).
40
+
41
+
# [Cloud-based solution](#tab/cloud)
36
42
37
43
Use the Device Provisioning Service (DPS) to provision devices at scale. DPS is a helper service for IoT Hub and IoT Central that enables zero-touch device provisioning at scale. To learn more, see [Best practices for large-scale IoT device deployments](../iot-dps/concepts-deploy-at-scale.md).
38
44
@@ -44,7 +50,7 @@ For a guide to scalability in an IoT Central solution, see [IoT Central scalabil
44
50
45
51
For devices that connect to an IoT hub directly or to an IoT hub in an IoT Central application, make sure that the devices continue to connect as your solution scales. To learn more, see [Manage device reconnections after autoscale](./concepts-manage-device-reconnections.md) and [Handle connection failures](../iot-central/core/concepts-device-implementation.md#best-practices).
46
52
47
-
IoT Edge can help to help scale your solution. IoT Edge lets you move cloud analytics and custom business logic from the cloud to your devices. This approach lets your cloud solution focus on business insights instead of data management. Scale out your IoT solution by packaging your business logic into standard containers, deploy those containers to your devices, and monitor them from the cloud. For more information, see [Azure IoT Edge](../iot-edge/about-iot-edge.md).
53
+
IoT Edge can help scale your solution. IoT Edge lets you move cloud analytics and custom business logic from the cloud to your devices. This approach lets your cloud solution focus on business insights instead of data management. Scale out your IoT solution by packaging your business logic into standard containers, deploy those containers to your devices, and monitor them from the cloud. For more information, see [Azure IoT Edge](../iot-edge/about-iot-edge.md).
-[IoT Hub Device Provisioning Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-iot-hub-device-provisioning-service-limits)
61
67
68
+
---
69
+
70
+
62
71
## High availability and disaster recovery
63
72
64
73
IoT solutions are often business-critical. You need to ensure that your solution can continue to operate if a failure occurs. You also need to ensure that you can recover your solution following a disaster.
65
74
75
+
# [Edge-based solution](#tab/edge)
76
+
77
+
# [Cloud-based solution](#tab/cloud)
78
+
66
79
To learn more about the high availability and disaster recovery capabilities the IoT services in your solution, see the following articles:
67
80
68
81
-[Azure IoT Hub](../iot-hub/iot-hub-ha-dr.md)
@@ -76,3 +89,5 @@ The following tutorials and guides provide more detail and guidance:
76
89
-[How to manually migrate an Azure IoT hub to a new Azure region](../iot-hub/migrate-hub-arm.md)
77
90
-[Manage device reconnections to create resilient applications (IoT Hub and IoT Central)](./concepts-manage-device-reconnections.md)
78
91
-[IoT Central device best practices](../iot-central/core/concepts-device-implementation.md#best-practices)
0 commit comments