Now that we've got a feel of mapping Lambda events with S3, let us give yet another service a go! This time its DynamoDB!
You can trigger Lambda functions in response to updates made to a particular DynamoDB table; for example, a new row that gets added in a table gets validated by a Lambda function, a row deletion operation resulting in Lambda sending a notification to a user, and so on. But, before you go ahead and implement triggers for DynamoDB, its important to note that, unlike S3, DynamoDB is a stream-based event source, which means that you first need to enable streams on your DynamoDB table before you create and map functions to it. Lambda actually polls the particular stream for events and when it finds ...
