Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best practise: Use 28 seconds as go to Lambda timeout #176

Open
victorskl opened this issue Mar 21, 2024 · 0 comments
Open

Best practise: Use 28 seconds as go to Lambda timeout #176

victorskl opened this issue Mar 21, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@victorskl
Copy link
Member

The Lambda timeout is, by default, 3 seconds. If this is ok for your task, please go for it.

Else it is advised to use 28s rule. This magic value is coming from the empirical observation from years of our current Portal operation.

Often, the data processing Lambda require more than 28 seconds. Then, please adjust your runtime requirement gradually. Just be critical and, think twice - to see whether you could improve the communication by leveraging async comm and, use Q when it makes sense.

If for the purpose of Lambda error and exception handling, please leverage its DLQ (to SQS Q) and, alarm when appropriate.

@victorskl victorskl added the documentation Improvements or additions to documentation label Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant