Artem Bilan

@tvrmsmith , Indeed, we can configure SQS queue to subscriber to the SNS topic. But how about if we will just have a Kinesis Binder and get a gain of...

I wonder why not Kinesis: https://github.com/spring-cloud/spring-cloud-stream-binder-aws-kinesis ? The SQS doesn't fit fully the SCSt communication model. There is no publish-subscribe semantics, no partition and offset management etc.

I see your point, @tvrmsmith . Thank you for sharing! Unfortunately we don't have resources to jump to this area. Contribution is welcome of course!

Ha-ha! No, that is big thanks to you, Community. Without your comprehensive feedback and valuable contributions the Spring wouldn't be so awesome! 😉

If you want to know my opinion, then I don't see reason in this binder since we have a Kinesis one. But if you insists, I can come back to...

@chrylis , Well, you know we ensure that with the `checkpoint` for each consuming shard and store an offset for the records in the DymanoDB table. So, I believe this...

Looks great at a glance! A couple remarks: * consider to rename all the *kinesis* variables to *sqs* 😉 . That's minor * I think you miss a big picture...

@maciejwalkowiak , first of all it is called `consumer group`. There is nothing to do with customers 😄 Your `@IntegrationConverter` is not visible as a bean for the `IntegrationConverterInitializer` because...

Closed as non-relevant to the project.

You probably are missing this condition: > NOTE: When `TRIM_HORIZON` shard iterator type is used, we need to take into account the time lag which happens during pointing the `ShardIterator`...