Lambda Deep Dive pt 5

invokes and targets

hello avatars, celt here to continue the lambda deep dive series with the invokes and targets. In the event driven architecture, which is one of the common cloud native patterns, being able to invoke Lambda synchronously or asynchronously. With targets, being able to chain together events and serverless compute, is another powerful pattern that facilitates automated workflows.

Lambda Triggers and Invokes

Lambda Invokes

Lambda Invoke API can be called either synchronously or asynchronously, by setting X-Amz-Invocation-Type: InvocationType to either RequestResponse or Event respectively. Additionally, the other possible argument is DryRun which is used to validate parameters and permissions.

The general tech difference here between synchronous and async is that with syncrounous the Lambda function will execute and send a response with the result as part of one request. More can be read on synchronous vs aysnc here.

Specifically to Lambda in sync vs async the path of the payload differs (this makes sense when you think of the paragraph above).

On a sync call the request goes directly to the invoke service (after hitting an aws managed load balanced endpoint) and then will make its way to a execution environment, if one does not exist, one will be created. We know that from previous parts of the deep dive.