Spring Integration for AWS 2.0.0.RC1 and Spring Cloud Stream Kinesis Binder 1.0.0.RC1 – Info Java

On Aug 3, 2018

What’s the Difference Between Java and JavaScript?

May 7, 2020

Why Java will remain a dominant language of the future

Dec 29, 2019

Both artifacts are available in the Spring Milestone repository and they can be consumed as maven dependencies:


    org.springframework.integration
    spring-integration-aws
    2.0.0.RC1



    org.springframework.cloud
    spring-cloud-stream-binder-kinesis
    1.0.0.RC1

Where the first one is not needed to be includes when the second one is in use.
The AWS Kinesis and AWS DynamoDB Java SDK dependencies are included transitively for AWS Kinesis Binder as well.
And now AWS DynamoDB Lock Client is also included for leader election.

Big thanks to the community for contribution and any feedback and especially for the help in testing these products in the real projects.

Here are changes since the previously announced Milestone 2:

A DynamoDbLockRegistry implementation has been added for distributed locking based on the AWS DynamoDB Lock Client foundation.
The KinesisMessageDrivenChannelAdapter can now be supplied with a LockRegistry and exclusive access to shards before consuming.
This way we ensure that only one consumer in a group reads records from the shard it is interested in.
When one consumer goes (yields leadership), some other consumer may acquire a lock for the shard and continue to consume from the stored checkpoint.
Some other bug fixes and improvements in various components throughout the Spring Integration AWS project.
The Kinesis Binder now exposes configuration properties for the underlying DynamoDbLockRegistry used for binder consumers.
Some other fixes have been done in Kinesis Binder project as well.

As usual any feedback, feature ideas, critics, bug reports and questions are welcome via appropriate communication channels!

We are aimed for GA release in a week or though.

Article Prepared by Ollala Corp