Yes, you can consume directly. However, adding the Kinesis abstraction later on will open your architecture for future use cases. You can use the Kinesis data streams for many other uses, including performing real time stream processing using Firehose or Data Analytics Stream.
Hi! Theoretically you can. But if you want these to stream indefinitely, you would need a web socket connection that is always open. Not sure how practical that is for this use case.
Very good tutorial. I like that Irtiza shows the errors. Helps me learn where to look when debugging my code.
You're welcome!
Amazing as always. Thank you Irtiza.
Thanks for always watching the videos. Really appreciate it : )
Thank you. Very nice tutorial.
Glad you found it helpful!
Good content, but the coffee cup taking half the screen space making the content so hard to see is an interesting approach to say the least .
Haha! I took that feedback and removed it from future videos.
Question, why do we need Kenesis in between? As Lambda can consume DynamoDb stream directly?
Yes, you can consume directly.
However, adding the Kinesis abstraction later on will open your architecture for future use cases. You can use the Kinesis data streams for many other uses, including performing real time stream processing using Firehose or Data Analytics Stream.
Also kinesis additionally has retention where lambda doesn't,where we can store data in kinesis and asynchronously process the data later
Can we push these changes to WebSocket?
Hi! Theoretically you can. But if you want these to stream indefinitely, you would need a web socket connection that is always open. Not sure how practical that is for this use case.
@@irtizahafiz We need to keep track of all connection in DynamoDB and we have to send message to each connection. This is not scalable solution.