Engineering
Releases
News and Events

Spring Integration AWS 2.2 GA and Spring Cloud Stream Kinesis Binder 1.2 GA Available

Today it’s my pleasure to announce General Availability of Spring Integration for Amazon Web Services extension version 2.2.0 and Spring Cloud Stream Binder for AWS Kinesis version 1.2.0.

These releases can be downloaded from Maven Central, JCenter, and our release repository:

compile "org.springframework.integration:spring-integration-aws:2.2.0.RELEASE"

If you don’t use Kinesis Binder. Or via Binder dependency:

compile "org.springframework.cloud:spring-cloud-stream-binder-kinesis:1.2.0.RELEASE"

The main theme of both these releases is about new functionality to support Kinesis Client and Kinesis Producer libraries. For this purpose the spring-integration-aws is shipped with KclMessageDrivenChannelAdapter and KplMessageHandler implementations, respectively. At the moment an implementation is based on the KCL v1.x, since not all AWS dependencies we use in the spring-integration-aws provide the AWS SKD v2 implementation. Based on the Kinesis Client Library investigation, an additional CheckpointMode.periodic has been introduced to both KclMessageDrivenChannelAdapter and KinesisMessageDrivenChannelAdapter.

The spring-cloud-stream-binder-kinesis is based on the recently released Spring Cloud Stream version 2.2 and provides a new Binder configuration option to enable KCL/KPL functionality:

spring.cloud.stream.kinesis.binder.kplKclEnabled = true

The KCL/KPL dependencies are included explicitly into the spring-cloud-stream-binder-kinesis, so there is just left a simple decision about selecting classical or KCL/KPL mode for Kinesis Binder.

Another new feature in the Kinesis Binder is for DynamoDB Streams, which can be handled as Kinesis Consumer records. For this purpose a particular input binding should be configured with the property:

spring.cloud.stream.kinesis.bindings.<channelName>.consumer.dynamoDbStreams = true

Also a configuration for the DynamoDB and Cloud Watch are optional now if your Spring Cloud Stream Microservice works only in a source mode. There is only need to worry about a Kinesis producer configuration, either classical or KPL mode.

Many thanks to everyone from the Community for all the feedback and contribution to these projects.

Any feedback is welcome via all the available communication channels!

Spring Integration for AWS resources:

Spring Cloud Stream Binder for AWS Kinesis resources:

comments powered by Disqus