simple321vip
155 lines
4.5 KiB
Markdown
155 lines
4.5 KiB
Markdown
# Azure
|
||
|
||
> 来源：原 mongodb 集合 `t_blog` · 整理日期：2026-08-25
|
||
> 分类 ID：`2022052309468900000000000004` · 排序：8 · 文章数：8
|
||
|
||
## 目录
|
||
|
||
1. [Iot Hub Endpoint](#iot-hub-endpoint)
|
||
2. [Iot Hub Message routing](#iot-hub-message-routing)
|
||
3. [Azure IoT Hub Device Provisioning Service (DPS)](#azure-iot-hub-device-provisioning-service-dps)
|
||
4. [Batch Shipyard](#batch-shipyard)
|
||
5. [Azure system](#azure-system)
|
||
6. [pricing](#pricing)
|
||
7. [Azure IoT Edge](#azure-iot-edge)
|
||
8. [pvc](#pvc)
|
||
|
||
---
|
||
|
||
## 1. Iot Hub Endpoint
|
||
|
||
<sub>bid: `2022052309469000000000000009`</sub>
|
||
|
||
### endpoints
|
||
---
|
||
[IoT Hub endpoints](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-endpoints)
|
||
|
||
## IoT Hub names
|
||
You can find the hostname of the IoT hub that hosts your endpoints in the portal on your hub's Overview page.
|
||
By default, the DNS name of an IoT hub looks like: {your iot hub name}.azure-devices.net.
|
||
|
||
## List of built-in IoT Hub endpoints
|
||
1. Device identity management
|
||
2. Device twin management
|
||
3. Jobs management
|
||
4. Device endpoints
|
||
5. Service endpoints
|
||
6. Resource provider.
|
||
|
||
## Custom endpoints
|
||
1. Azure Storage containers
|
||
2. Event Hubs
|
||
3. Service Bus Queues
|
||
4. Service Bus Topics
|
||
|
||
|
||
## Endpoint Health
|
||
|
||
## Field gateways
|
||
In an IoT solution, a field gateway sits between your devices and your IoT Hub endpoints.
|
||
It is typically located close to your devices.
|
||
You can use Azure IoT Edge to implement a field gateway.
|
||
IoT Edge offers functionality such as multiplexing communications from multiple devices onto the same IoT Hub connection.
|
||
|
||
---
|
||
|
||
## 2. Iot Hub Message routing
|
||
|
||
<sub>bid: `2022052310025600000000000010`</sub>
|
||
|
||
Message routing
|
||
---
|
||
[Message routing](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c)
|
||
|
||
---
|
||
|
||
## 3. Azure IoT Hub Device Provisioning Service (DPS)
|
||
|
||
<sub>bid: `2022052310265300000000000011`</sub>
|
||
|
||
### Azure IoT Hub Device Provisioning Service (DPS)
|
||
---
|
||
[DPS](https://docs.microsoft.com/en-us/azure/iot-dps/?WT.mc_id=Portal-Microsoft_Azure_IotHub)
|
||
|
||
## what is
|
||
Microsoft Azure provides a rich set of integrated public cloud services for all your IoT solution needs.
|
||
The IoT Hub Device Provisioning Service (DPS) is a helper service for IoT Hub that enables zero-touch, just-in-time provisioning to the right IoT hub without requiring human intervention.
|
||
DPS enables the provisioning of millions of devices in a secure and scalable manner.
|
||
|
||
##
|
||
|
||
---
|
||
|
||
## 4. Batch Shipyard
|
||
|
||
<sub>bid: `2022052313361500000000000012`</sub>
|
||
|
||
## Batch Shipyard
|
||
---
|
||
[doc](https://batch-shipyard.readthedocs.io/en/latest/00-introduction/)
|
||
|
||
---
|
||
|
||
## 5. Azure system
|
||
|
||
<sub>bid: `2022052313512900000000000013`</sub>
|
||
|
||
1.active directory
|
||
2.subscriptions
|
||
3.Resource groups
|
||
4.
|
||
|
||
azure 基本上是个网格体系
|
||
|
||
---
|
||
|
||
## 6. pricing
|
||
|
||
<sub>bid: `2022052314413800000000000015`</sub>
|
||
|
||
## Pricing Options
|
||
---
|
||
[doc](https://azure.microsoft.com/ja-jp/pricing/details/iot-hub/#purchase-options)
|
||
|
||
---
|
||
|
||
## 7. Azure IoT Edge
|
||
|
||
<sub>bid: `2022052410596000000000000017`</sub>
|
||
|
||
## Modules
|
||
---
|
||
[doc](https://docs.microsoft.com/en-us/azure/iot-edge/iot-edge-modules?view=iotedge-2020-11)
|
||
|
||
IoT Edge modules are Docker containers deployed to IoT Edge devices.
|
||
They can communicate with other modules or send data to the IoT Edge runtime.
|
||
Azure IoT Edge lets you deploy and manage business logic on the edge in the form of modules.
|
||
Azure IoT Edge modules are the smallest unit of computation managed by IoT Edge, and can contain Azure services (such as Azure Stream Analytics) or your own solution-specific code.
|
||
To understand how modules are developed, deployed, and maintained, consider the four conceptual elements of a module:
|
||
|
||
## Routes
|
||
---
|
||
[doc](https://docs.microsoft.com/ja-jp/azure/iot-edge/module-composition?view=iotedge-2020-11#declare-routes)
|
||
|
||
|
||
## IoT Edge deployments
|
||
---
|
||
[doc](https://docs.microsoft.com/ja-jp/azure/iot-edge/module-deployment-monitoring?view=iotedge-2020-11)
|
||
|
||
IoT Edge deployments configure sets of IoT Edge devices to run IoT Edge modules.
|
||
Each deployment continuously ensures that all matching devices are running the specified set of modules, even when new devices are created or are modified to match the target condition.
|
||
|
||
Two modules are required in every deployment manifest: $edgeAgent, and $edgeHub.
|
||
|
||
These modules are part of the IoT Edge runtime that manages the IoT Edge device and the modules running on it.
|
||
|
||
---
|
||
|
||
## 8. pvc
|
||
|
||
<sub>bid: `2022110910113500000000000002`</sub>
|
||
|
||
|
||
|
||
---
|