Panda Insights

  Previous post deals with AWS lambda and java. Before we go to the hands on of lambda part I would like to introduce Kinesis. The reason being Lambda is almost always used in conjunction with another services. And the other service in our case will be Kinesis. Because Kinesis is a bigger topic we will be covering this in in 3 parts. Links to subsequent blogs   A kinesis stream : Kinesis Fundamentals and the design we will be following in the post Kinesis Producer : creating a stream and publishing into the stream using both SDK API and KPL and also the kinesis agent. A kinesis consumer : A lambda function which runs whenever a message is published into the stream Kinesis streams:  A managed message streaming service provided by AWS, comparable to Apache Kafka with subtle differences. It comes in variants of provisioned and on-demend variants. Provisioned service is selected when we know and we can control the amount of data coming in per second while on-demand is ...

This is the second post of the series in which we look at the different Kinesis Producers and their usage in a Java based SDK environment. For knowing details of Kinesis or the consumer you can visit below links A kinesis stream : Kinesis Fundamentals and the design we will be following in the post Kinesis Producer : creating a stream and publishing into the stream using both SDK API and KPL and also the kinesis agent. A kinesis consumer : A lambda function which runs whenever a message is published into the stream The code for this post can be found here . Kinesis Producer:  This is a spring boot application which is meant to run as an independent application. It could be deployed into the EC2 instance/ECS or run as a third party. For our purpose we are running this locally to publish messages into the producer. T here are 4 different mechanisms of producing messages. 2 using SDK APIs and another 2 using KPL libraries.All 4 are covered here.Let us dive into the code...