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

New Serverless Pattern - Priority Queue using SQS #1765

Conversation

biswanathmukherjee
Copy link
Contributor

Description of changes:

This sample project showcases Priority Queue Pattern using AWS Serverless services. There are three priorities - High, Medium and Low. The project demonstrates the behavior using both standard and FIFO SQS Queues. Lambda is used as consumer of the messages from SQS queues. The objective is to first process the messages from High priority queue and only if there is no messages in High priority queue, process from Medium and subsequently from Low priority queue if no more messages left on High and Medium priority queues. As it is observed in the results, FIFO queue performs much better in maintaining the priority however Standard queue might not be able to maintain the priority in some instances as the ordering of the messages is on best effort basis.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@julianwood
Copy link
Contributor

Hi, thanks for the submission. This pattern seems overly complex.
I suggest adding this as a repo on aws-samples which we can link to via the repo submissions.
Also, this patterns could have issues if the queues scale. If it takes longer than 15 minutes to drain all queues, for example, this will fail.
I'm not sure this is a good architectural pattern, DM me if you'd like to discuss further.

@julianwood
Copy link
Contributor

Closing to move to repo

@julianwood julianwood closed this Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants