Best Practice 19.2 – Evaluate network connectivity and data freshness requirements
It enables you to make the right assumptions on the local data storage and data transmission needed to satisfy the requirements of your workload. It also provides a clear understanding of the requirements of the workload and allows you to determine the hardware and software needs of the devices and the platform.
Recommendation 19.2.1 - Choose the right Quality of Service (QoS) for publishing the messages
-
QoS 0 should be the default choice for all telemetry data that can cope with message loss and where data freshness is more important than reliability.
-
QoS 1 provides reliable message transmission at the expense of increased latency, ordered ingestion in case of retries, and local memory consumption. It requires a local buffer for all unacknowledged messages.
-
QoS 2 provides once and only once delivery of messages but increases the latency.
Recommendation 19.2.2 – Right size the offline persistent storage to ensure your application objective can be obtained without wasting resources
-
The AWS IoT Greengrass message spooler can be configured with an offline message queue for messages that need to be sent to the AWS IoT Core. The size and type of storage should be configured according to the needs of the workload.
-
For more:
