Thank you for the video! This is great for explaining concepts. It would have been even better if the use-case was explained more in-depth, even if this is an imaginary scenario. it is not clear to me how it would benefit having a Lambda that reads from Kinesis, to then dump the data into a DB. (Isn't Kinesis already dumping data in a DDB behind the curtains? the ddb which basically allows for replay...?) If you could add that, that would help clear up the real-world usefulness of that, just like you illustrated real-life usefulness with the sports betting in the previous videos. I thought Kinesis already does the storage part, as mentioned in the other videos in this playlist. Do we wish to store to DDB for longer than Kinesis does? Basically have long-term storage? And if yes, why DDB and not S3 then? But then again: perhaps these are questions out of scope for the purpose of just explaining Kinesis Data Streams concepts... I am just saying it would help having the greater scope of this... Also: - how can "poison" messages get into a data stream? And what "poison" messages be more precisely? - the video mentions "partitions" at 1:38 but does not expand on what partitions are.
Hi there. While we can't provide an immediate response on this, we have referred your question for internal review. Meanwhile, we suggest reaching out to our community of helpful specialists at re:Post: go.aws/aws-repost. Feel free to copy the URL and add any questions you may have. ^ZP
Sorry for the trouble! I recommend posting your use case on re:Post, where our community of gurus can chime in: go.aws/aws-repost. 💬 For additional help options, review this re:Post article: go.aws/get-help. 🧐 ^KB
That's a great question! Our experts and enthusiasts may be able to dive deeper into this with you, feel free to provide details on your use case, here: go.aws/aws-repost. 📝 ^RM
This really depends on what you're trying to do. There are pros/cons to using it, and much can be said for any of the services. Ask yourself if your architecture needs to use Kinesis, and make sure you answer for WHY; what problems does it solve for you.
![AWS Kinesis Tutorial for Beginners [FULL COURSE in 65 mins]](/img/1.gif)
Thank you for the video! This is great for explaining concepts.
It would have been even better if the use-case was explained more in-depth, even if this is an imaginary scenario.
it is not clear to me how it would benefit having a Lambda that reads from Kinesis, to then dump the data into a DB. (Isn't Kinesis already dumping data in a DDB behind the curtains? the ddb which basically allows for replay...?) If you could add that, that would help clear up the real-world usefulness of that, just like you illustrated real-life usefulness with the sports betting in the previous videos. I thought Kinesis already does the storage part, as mentioned in the other videos in this playlist. Do we wish to store to DDB for longer than Kinesis does? Basically have long-term storage? And if yes, why DDB and not S3 then?
But then again: perhaps these are questions out of scope for the purpose of just explaining Kinesis Data Streams concepts... I am just saying it would help having the greater scope of this...
Also:
- how can "poison" messages get into a data stream? And what "poison" messages be more precisely?
- the video mentions "partitions" at 1:38 but does not expand on what partitions are.
Hi there. For assistance with your question, you’re welcome to post it on our re:Post community of experts, here: go.aws/aws-repost. ^RZ
can you explain the kinesis-lambda-demo-role that you have selected while setting up the lambda function.
Hi there. While we can't provide an immediate response on this, we have referred your question for internal review. Meanwhile, we suggest reaching out to our community of helpful specialists at re:Post: go.aws/aws-repost. Feel free to copy the URL and add any questions you may have. ^ZP
kinesis triggers are not working for cross-account scenario.
Sorry for the trouble! I recommend posting your use case on re:Post, where our community of gurus can chime in: go.aws/aws-repost. 💬 For additional help options, review this re:Post article: go.aws/get-help. 🧐 ^KB
so the flow is source-->kinesis-->lambda-->dynamodb. why can't we do source-->lambda-->dynamodb instead ?
That's a great question! Our experts and enthusiasts may be able to dive deeper into this with you, feel free to provide details on your use case, here: go.aws/aws-repost. 📝 ^RM
This really depends on what you're trying to do. There are pros/cons to using it, and much can be said for any of the services. Ask yourself if your architecture needs to use Kinesis, and make sure you answer for WHY; what problems does it solve for you.