SlideShare a Scribd company logo

Serverless lessons learned #5 retries

•Download as PPTX, PDF•
•
M
Maik Wiesmüller

When we started building serverless applications back in 2017, there was quite a lot to learn. So we'd like to share some mistakes, important pieces, and concepts for production-ready serverless projects. This time: Retries. More Information: API-Retries: https://lnkd.in/dVwwEsat Lambda-Retries: https://lnkd.in/dEs6xXyb SQS-Retries: https://lnkd.in/dPm2x7ZT

1 of 11
Retries ? Serverless on AWS lessons learned #5 Are you really production-ready?
AWS Services calls are made over a network via REST- APIs. Conveniently wrapped by the AWS SDK.
A lot of components in a network can* fail! *will at some point ● DNS errors ● faulty switches ● load balancer and more...
A common approach in distributed systems is implementing retry mechanisms. And so did AWS!
Where is the problem?
Errors will occur! Retries will be made! Events will be processed twice! Unexpected behavior!
Retries are awesome, if you are well aware of how, when and where they can happen.
Make sure you are aware of retries and understand the behavior of your used services and SDKs! more information and links in the description
Examples AWS SDK service calls 5XX & throttling SQS lambda subscription Lambda async invocation
Retries
thumbs up, comment, share What are your thoughts? Is anything important missing? If you liked it, please leave a comment. connect with me!

More Related Content

Serverless lessons learned #5 retries