A thought based on the question: Kinesis and SQS operate differently. So when you say "the shard will be blocked" - individual consumers on the shard might choose not to consume the next message in the stream but there's no concept of "blocking". Unlike SQS, messages in the stream are visible to all of the consumers so they can choose what they're going to do with each message - which is great if you have several different processes that need to happen on a single message - you can use different consumers and they don't get in each other's way.
So in the Kinesis world, if you want to maintain ordering you can only have a single consumer on the stream (shard, really). If there is a fault the blocking happens in the consumer, not in Kinesis.
Probably not helpful - but I'd question why Kinesis is better than SQS FIFO in this case.
Finally: I'm a little concerned about the comment "SQS FIFO is too slow" - have you tested Kinesis to ensure that it meets your performance requirements?
Given the complexity of the question and the challenges you appear to be facing I'd contact your local AWS Solutions Architect to discuss further...
- Accepted Answerasked 8 years ago
- Why am I getting a 554 or 400 "Message rejected" error with the message "Email address is not verified" from Amazon SES?AWS OFFICIALUpdated 2 years ago
- How do I create, configure, and troubleshoot a subscription filter to Kinesis using the CloudWatch console?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- EXPERTpublished 5 months ago