1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
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.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 6 Monaten- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 6 Monaten
- Wie veröffentliche ich MQTT-Nachrichten von meinem Gerät auf AWS IoT Core, wenn ich Python verwende?AWS OFFICIALAktualisiert vor 3 Jahren
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
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:
https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html#mqtt-differences