Best Practice 13.2 – Implement retry and backoff logic to support throttling by device type - IoT Lens Checklist

Best Practice 13.2 – Implement retry and backoff logic to support throttling by device type

Retry and backoff logic should be implemented in a controlled manner so that when you need to alter throttling settings per device type, you can easily do it. Using data storage of any chosen kind gives you flexibility on what data to publish down to the device.

Recommendation 13.3.1 – Use storage mechanisms that enable retry mechanisms

  • Using DynamoDB, you can hold data in key value format where device ID is the key. Retry logic can be applied to only certain device ID’s.

  • Using Amazon Relational Database Service (Amazon RDS), you have the flexibility to use a variety of database engines. The retry messages can have new real-time data augmented with historic data from previous device interactions stored in RDS.

  • AWS IoT Events provides state machines with built-in timers to hold back data and retry based on timers.