Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a version of the adapter for KCL v2.x #42

Open
artur-jablonski opened this issue Nov 30, 2020 · 6 comments
Open

Is there a version of the adapter for KCL v2.x #42

artur-jablonski opened this issue Nov 30, 2020 · 6 comments

Comments

@artur-jablonski
Copy link

As per title. I am looking at consuming dynamodb stream via KCL and ended up here.
I need to use KCL v2.x, but this library seems to be dealing with KCL v1.x.
Is there an equivalent implementation for KCL v2.x?

@gjesse
Copy link

gjesse commented Dec 9, 2020

I'm not a member of the project but i went through this a while back and concluded that, no, there is not.

@artur-jablonski
Copy link
Author

Same conclusion. On the good side, seems like dynamodb has a new
feature to stream directly to Kinesis.

@gjesse
Copy link

gjesse commented Dec 9, 2020

whoa.. thanks for the heads up. that looks great!

@mustafaakin
Copy link

Why pay extra for Kinesis when DynamoDB Streams exist? I looked at the how to implement my own but looks complex for now.

@dacevedo12
Copy link

dacevedo12 commented Sep 27, 2022

Any updates?

awslabs/amazon-kinesis-client#451

@olbat
Copy link

olbat commented Sep 6, 2023

@artur-jablonski , I think that Kinesis can only be an easy alternative for some use cases.

Here are some key differences:

Change data capture for DynamoDB Streams:

DynamoDB Streams helps ensure the following:

  • Each stream record appears exactly once in the stream.
  • For each item that is modified in a DynamoDB table, the stream records appear in the same sequence as the actual modifications to the item.

Kinesis Data Streams to capture changes to DynamoDB:

The Kinesis data stream records might appear in a different sequence than the item changes occurred. The same item notifications might also appear more than once in the stream. You can check the ApproximateCreationDateTime attribute to identify the approximate order that the item modifications occurred, and to identify duplicate records. ApproximateCreationDateTime indicates the time of the modification in milliseconds.

Therefore, depending the the use-case, one might not easily be able to trade one for the other (e.g. if the application needs the guarantee that messages appear in order of modification in the change stream).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants