Lambda will throw the message away, and the customer will never get the service. What happens if their API is down for more than 5 minutes?
#Aws lambda python encrypto code
So in the case of the Lambda function code returning an error or failing, the Lambda execution will be attempted again up to 3 times over a 5 minute period. The retry interval increases exponentially from 1 second after the first attempt to a maximum of 5 minutes. If the function returns an error, Lambda attempts to run it two more times, with a one-minute wait between the first two attempts, and two minutes between the second and third attempts.įor throttling errors (429) and system errors (500-series), Lambda returns the event to the queue and attempts to run the function again for up to 6 hours. Lambda manages the function’s asynchronous event queue and attempts to retry on errors. Of course, Lambda could go down, but then the whole of my application would be out of action anyway, so what matters even more in this case is how Lambda retries in the face of failure. However, the target in my case is AWS Lambda, not the 3rd party API directly.
If you read through the docs, you’ll find that EventBridge automatically retries hitting targets for 24 hours.īy default, EventBridge retries sending the event for 24 hours and up to 185 times with an exponential back off and jitter, or randomized delay. However, we would still need to get that 3rd API call made, when their API comes back up. We can still trade and take on new customers even if the 3rd party API is temporarily down. This event-driven approach decouples completing the financial transaction and calling the 3rd party API. To do this, I subscribed a Lambda function to the EventBridge bus, and called their API in program code. In the project, when a new item is sold, a 3rd party API must be called to register the customer for a service. I’ve been building a system that uses EventBridge as the event bus to notify other systems about key events. ← Home Setting up an encrypted AWS Lambda dead letter queue with Go CDK
0 kommentar(er)
