After building serverless applications for a couple of years now, we decided to share some important pieces and concepts for production-ready serverless projects. Let's start with: What are Custom SDK Timeouts and why you should care. Default timeouts and troubleshooting: https://lnkd.in/dZsgxk9p

1. Custom SDK Timeouts
?
Serverless on AWS
lessons learned #1
Are you really
production-ready?

2. Serverless projects
are highly distributed
systems.
Everything
communicates over
the network.

3. The following
will happen:
Services answer slowly.
Network hiccups!

4. Why does it matter?

5. AWS SDK has default
values for connection
and socket timeouts.
Varying from 10 to 300
seconds.

6. For a slow service, 10
seconds might be too
quick.
And 300 seconds are
too much to wait for a
connection retry.

7. Your lambda function
timeout does not care
about those settings.
Which might cause
seemingly strange
function timeouts.

8. How?

9. Test different
configurations and
measure timings.
Update appropriate
values with AWS SDK
Config object.
*link with more details in description

10. Custom SDK Timeouts

11. thumbs up, comment, share
What are your thoughts?
Is anything important missing?
If you liked it, please leave a comment.
connect with me!