We talk a lot about more advanced level of Lambda triggers in our popular “Complete Guide to Lambda Triggers” series, Part 1 and Part 2 out now. So, this time, we’re bringing it back to the basics because skipping some steps when learning something new might get you confused, it tends to get annoying, or it can even make you frustrated. Why? Well, to be able to understand how something works appropriately and later on to know how to implement your knowledge practically without any kind of stress involved, you must master everything about there is regarding the particular subject in particular order. Let me put it this way…
_ You can’t calculate how fast is subatomic particle moving in space if its 300 light-years away from the closest planet if you don’t know the basic math like 3.14 times 42, right?_
Baby steps first. So, going back to our topic here, what are AWS Lambda triggers?
AWS Lambda And Amazon DynamoDB Integration
DynamoDB is an AWS product just as AWS Lambda and therefore you’re able to create triggers with ease. Triggers are pieces of code that will automatically respond to any events in DynamoDB Streams.
Triggers allow you to build applications which will then react to any data modification made in DynamoDB tables. By enabling DynamoDB Streams on a table, you will be able to associate an ARN with your Lambda function. Instantly after any item in the table is modified, a new record will appear in the table’s stream. When AWS Lambda detects a new stream record, it will invoke your Lambda function synchronously.
Lambda functions are able to perform any actions you specify, like sending notifications or a workflow initiation. A simple example of that would be if we suppose you have a mobile gaming app that’s writing on a GameScores table, so, each time the TopScore attribute of the GameScores table is updated, a corresponding stream record will be written to the table’s stream. This means that this event can trigger a Lambda function that will post a message of social media sites.
#aws lambda #aws
