The IoT Hub provides the device with cloud messaging through the event hub endpoint. Concentrations of events have a retention time expressed in days. This is a data stream that the read client could reread more time, because the cursor is on the client side (and not on the server side, like queues and threads). With an IoT hub, the default associated storage time is 1 day, but you can change it.
If you want to store received messages from the device, you need the client to view the endpoint of the Event Hubs (for example, using the Processor Processor node), which has business logic for processing messages and storing them in a database for example.
Of course, you can use a different decoupling layer so that the client reads from event concentrators and stores messages in queues. Then you have another client, which at its own pace reads from the queues and stores in the database. This way you have the fast path event nodes.
source share