领域
Embedded & IoT
技能档案
MQTT: pub/sub, QoS levels, retained messages, MQTT 5, broker (Mosquitto, EMQX)
角色数
2
包含此技能的角色
级别数
5
结构化成长路径
必要要求
8
其余 2 个可选
Embedded & IoT
IoT Platforms
2026/3/17
选择当前级别并对比期望。下方卡片显示晋升所需掌握的内容。
表格展示从初级到首席的技能深度变化。点击行查看详情。
| 角色 | 必要性 | 描述 |
|---|---|---|
| Embedded Developer | 必要 | Understands the fundamentals of MQTT Protocol. Applies basic practices in daily work. Follows recommendations from the team and documentation. |
| IoT Engineer | Connects IoT devices to MQTT broker (Mosquitto). Publishes sensor data to topics and subscribes to commands. Understands QoS 0/1/2 and retained messages. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| Embedded Developer | 必要 | Implements MQTT communications: QoS 1/2, retained messages, last will, topic hierarchy design. Optimizes reconnect and keep-alive for unstable networks. |
| IoT Engineer | Designs MQTT topic hierarchy for IoT projects. Uses MQTT 5.0 features: shared subscriptions, message expiry. Configures TLS and client certificates for security. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| Embedded Developer | 必要 | Designs MQTT architecture for IoT fleet: shared subscriptions, broker bridging, MQTT 5.0 features. Implements TLS and client certificate authentication. |
| IoT Engineer | 必要 | Designs scalable MQTT infrastructure for IoT platform: EMQX/VerneMQ clustering, bridging, routing rules. Implements CoAP for constrained devices. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| Embedded Developer | 必要 | Defines MQTT strategy for IoT platform. Establishes topic naming conventions, QoS policy, security standards for device fleet. |
| IoT Engineer | 必要 | Defines messaging standards for IoT platform. Selects protocols (MQTT/AMQP/CoAP) for different scenarios. Establishes topic naming conventions and governance. |
| 角色 | 必要性 | 描述 |
|---|---|---|
| Embedded Developer | 必要 | Shapes MQTT/messaging strategy for IoT platform: broker architecture, protocol versioning, security standards for device fleet. Evaluates alternatives (AMQP, DDS) for specific use cases. |
| IoT Engineer | 必要 | Defines enterprise IoT messaging strategy. Evaluates Sparkplug B, Unified Namespace approaches. Builds architecture for millions of devices. |