Skip to content

Commit 59311f5

Browse files
committed
Address feedback
1 parent e42a71d commit 59311f5

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/iot/iot-overview-device-development.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,13 @@ The following diagram shows a high-level view of the components in a typical edg
2121

2222
:::image type="content" source="media/iot-overview-device-development/iot-edge-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting asset connectivity areas." border="false":::
2323

24-
Assets typically have built-in firmware that that implements standard protocols. For example, a robotic arm might be an OPC UA client and a security video might implement ONVIF. Azure IoT Operations includes various connectors that can use these protocols to assets, and translate messages from the assets into MQTT messages. You can create your own, custom connectors to connect to assets that use protocols not natively supported by Azure IoT Operations.
24+
Assets typically have built-in firmware that that implements standard protocols. For example, a robotic arm might be an OPC UA client and a security video camera might implement ONVIF. Azure IoT Operations includes various connectors that can use these protocols to communicate with assets and translate messages from the assets into MQTT messages. Some assets can receive messages enabling you to perform operations on them such as:
25+
26+
- Pan or tilt a security camera.
27+
- Change the logging level on a robotic arm.
28+
- Initiate a firmware update.
29+
30+
You can create your own, custom connectors to connect to assets that use protocols not natively supported by Azure IoT Operations.
2531

2632
# [Cloud-based solution](#tab/cloud)
2733

@@ -80,7 +86,7 @@ Examples of specialized hardware and operating systems include:
8086

8187
[Eclipse ThreadX](https://github.com/eclipse-threadx/rtos-docs) is a real time operating system for IoT and edge devices powered by MCUs. Eclipse ThreadX is designed to support highly constrained devices that are battery powered and have less than 64 KB of flash memory.
8288

83-
[Azure Sphere](/azure-sphere/product-overview/what-is-azure-sphere) is a secure, high-level application platform with built-in communication and security features for internet-connected devices. It comprises a secured, connected, crossover MCU, a custom high-level Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
89+
[Azure Sphere (Integrated)](/azure-sphere/product-overview/what-is-azure-sphere?view=azure-sphere-integrated) is a secure, high-level application platform with built-in communication and security features for internet-connected devices. It comprises a secured, connected, crossover MCU, a custom high-level Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
8490

8591
### Device primitives
8692

@@ -175,6 +181,8 @@ Containerization is a way to package and run your code in a lightweight, isolate
175181

176182
Azure IoT Operations containerizes all its connectors, brokers, and other components that run on the edge. Azure IoT Edge deploys to a Kubernetes cluster, which is a container orchestration platform. Deploy any custom connectors or other components that you create to the Kubernetes cluster.
177183

184+
You can view a solution that uses Azure IoT Edge as an edge-based gateway to IoT Hub as a hybrid solution that includes elements of both edge-based and cloud-based solutions.
185+
178186
# [Cloud-based solution](#tab/cloud)
179187

180188
If you use containers, such as in Docker, to run your device code you can deploy code to your devices by using the capabilities of the container infrastructure. Containers also let you define a runtime environment for your code with all the required library and package versions installed. Containers make it easier to deploy updates and to manage the lifecycle of your IoT devices.

0 commit comments

Comments
 (0)