IoT solution scalability, high availability, and disaster recovery
This overview introduces the key concepts around the options for scalability, high availability, and disaster recovery in an Azure IoT solution. Each section includes links to content that provides further detail and guidance.
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the areas relevant to scalability, high availability, and disaster recover in an IoT solution.
IoT solution scalability
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.
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.
Use the Device Update for IoT Hub helper service to manage over-the-air updates to your devices at scale.
You can scale the IoT Hub service vertically and horizontally. For an automated approach, see the IoT Hub autoscaler sample. Use IoT Hub routing to handle scaling out the services that IoT Hub delivers messages to. To learn more, see IoT Hub message routing.
For a guide to scalability in an IoT Central solution, see IoT Central scalability. If you're using private endpoints with your IoT Central solution, you need to plan the size of the subnet in your virtual network.
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 and Handle connection failures.
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.
Service tiers and pricing plans:
- Choose the right IoT Hub tier and size for your solution
- Choose the right pricing plan for your IoT Central solution
Service limits and quotas:
- Azure Digital Twins
- Device Update for IoT Hub limits
- IoT Central limits
- IoT Hub limits
- IoT Hub Device Provisioning Service limits
High availability and disaster recovery
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.
To learn more about the high availability and disaster recovery capabilities the IoT services in your solution, see the following articles:
- Azure IoT Hub
- Device Provisioning Service
- Azure Digital Twins
- Azure IoT Central high availability and disaster recovery
The following tutorials and guides provide more detail and guidance:
- Tutorial: Perform manual failover for an IoT hub
- How to manually migrate an Azure IoT hub to a new Azure region
- Manage device reconnections to create resilient applications (IoT Hub and IoT Central)
- IoT Central device best practices
Next steps
Now that you've seen an overview of the extensibility options available to your IoT solution, some suggested next steps include: