| ID | product.ingestion |
|---|---|
| Description | Cloud-side ingestion of device telemetry and commands. |
| Key | ingestion |
| Type | system |
| Team | Ingestion |
| Owner | ingestion@iotgateway.example |
| Status | active |
| Technologies | Go, EMQX/Mosquitto (MQTT), MQTT, TLS |
| Attributes | protocol: MQTT 5.0, throughput: 1M msgs/s |
| Tags |
Ingestion is the front door of the platform. Every connected device opens a secure session here, streams its telemetry up, and receives cloud-to-device commands back down. If a device can talk to the cloud at all, it is talking to Ingestion first.
Responsibility in one sentence
Terminate millions of secure device connections, fan telemetry into the processing pipeline, and reliably deliver commands back to each device.
Could not build diagram for model "example-iot".
The telemetry alert pipeline begins with messages that arrive here:
Commands dispatched from the cloud are delivered to devices through this system:
New devices establish their first secure session as part of provisioning:
And firmware rollouts ride the same command and telemetry paths:
1 incoming link · 2 outgoing links
| Source object | Label | Link type | Relation | Raw id | Required | Description | |
|---|---|---|---|---|---|---|---|
| publishes to | — | links | product.ingestion | — | — |
| Target object | Label | Link type | Relation | Raw id | Required | Description | |
|---|---|---|---|---|---|---|---|
| feeds | — | links | product.processing | — | — | ||
| forwards device events to | — | links | product.device_management | — | — |