IoT Core to Kinesis

I can define action in IoT message rule and push data to Kinesis Data Stream(single shard). Since Kinesis is going to assign sequence number to the messages as they come from Iot Core. Is there any scalability issue between iot core and Kinesis because of single shard. Example IoT core receives 1000 message and rules redirect all of them to Kinesis. Will kinesis be able to handle? what is the capacity?

トピック

モノのインターネット (IoT)分析

タグ

AWS IoT Core Amazon Kinesis

言語

English

Ozy smile

質問済み 2年前317ビュー

1回答

新しい順
投票が多い順
コメントが多い順

これらの回答は役に立ちましたか？コミュニティがあなたの知識を活用できるように、正解に賛成票を投じてください。

Hi Ozy smile. Please refer to the Kinesis Data Streams quotas and limits: https://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html

A single shard can ingest up to 1 MB of data per second (including partition keys) or 1,000 records per second for writes. Similarly, if you scale your stream to 5,000 shards, the stream can ingest up to 5 GB per second or 5 million records per second. If you need more ingest capacity, you can easily scale up the number of shards in the stream using the AWS Management Console or the UpdateShardCount API.

エキスパート

Greg_B

回答済み 2年前

Ozy smile
2年前
Thanks you for the answer, one more quick question, if I increase the number of the shards, is sequencing/ordering will be valid only in same shard? I mean is each shard independent from each other? Thanks
Greg_B エキスパート
2年前
I'm quite sure the ordering is per shard, but struggling to find a documentation reference to point to. The sequence number is "unique per partition-key within its shard": https://docs.aws.amazon.com/streams/latest/dev/key-concepts.html#sequence-number

Please be aware that for AWS IoT Core:

The message broker doesn't guarantee the order in which messages and ACK are received.

https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html#mqtt-differences

IoT Core to Kinesis

関連するコンテンツ