Skip to content

Created alternate function #3

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Oct 15, 2020
Merged

Created alternate function #3

merged 1 commit into from
Oct 15, 2020

Conversation

jon-frame
Copy link
Contributor

Existing function does not leverage the SQS messages in the lambda event and instead polls the queue again, meaning once function gets up to speed with concurrent invocations, the queue is perpetually empty: only 5-7 messages make it into DynamoDB, then no more. This fix instead uses the Lambda event to push messages into DynamoDB.

Existing function does not leverage the SQS messages in the lambda event and instead polls the queue again, meaning once function gets up to speed with concurrent invocations, the queue is perpetually empty: only 5-7 messages make it into DynamoDB, then no more. This fix instead uses the Lambda event to push messages into DynamoDB.
@mrichman
Copy link
Contributor

I'm likely the only one to see this, and since I don't work here anymore, I can't merge your PR. Sorry.

@jon-frame jon-frame merged commit c037e4a into linuxacademy:master Oct 15, 2020
iMaguz added a commit to iMaguz/content-lambda-boto3 that referenced this pull request Jul 9, 2023
This reverts commit c037e4a, reversing
changes made to 33f15a4.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants