Use SNS instead of SQS for communication between Producer and Consumer #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
The Lambda handler was short-polling SQS, which resulted in a very large number of API requests to SQS.
This activity was consuming a significant portion of my free monthly tier of SQS. I fixed this issue by using SNS instead of SQS.
This change may result in reduced message ordering accuracy (unless we use FIFO queues instead of standard ones).
Since the events are not triggered frequently, this may not pose any significant issues. The solution has been working well in my environment.
This repository solution has been very helpful in reducing costs. Thanks!
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.