Note:
This is complete discovery currently, it is not expected that it will work, nor does it...
Please do not attempt to use it.
Resolves #397
Description:
The aim of this PR is to add the ability to execute SQS Consumer concurrently, meaning that it will keep triggering polls past the batch size and while other messages are being processed, up to a concurrent limit.
Type of change:
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Why is this change required?:
Currently, SQS Consumer restricts the amount of messages that can be processed to the batch size from AWS, this means that users are limited to processing a maximum of 10 messages at a time.
Code changes:
Added a new constants file that contains an enum for polling status values
Added a new option for concurrency that allows the user to configure the limits
Split the poll timeout functionality into a new function so it can be called from multiple places
Added tracking for the amount of concurrent executions
Adjusted the logic to queue a poll while messages are processing.
Updated status method to return concurrency and polling status
[ ] Add a new timeout value option for the amount of time to wait when the concurrent count has been reached (currently this is the normal timeout count, which may be wrong for some users)
[ ] Add unit/integration tests
[ ] Check that this works in the real world with a canary release (while still in PR)
[ ] Our users don't have concurrency right now, how might this affect them? This is most likely a breaking change any way, but we should check that there are no negative effects.
Resolves #397
Description:
The aim of this PR is to add the ability to execute SQS Consumer concurrently, meaning that it will keep triggering polls past the batch size and while other messages are being processed, up to a concurrent limit.
Type of change:
Why is this change required?:
Currently, SQS Consumer restricts the amount of messages that can be processed to the batch size from AWS, this means that users are limited to processing a maximum of 10 messages at a time.
Code changes:
Added a new constants file that contains an enum for polling status values
Added a new option for
concurrencythat allows the user to configure the limitsSplit the poll timeout functionality into a new function so it can be called from multiple places
Added tracking for the amount of concurrent executions
Adjusted the logic to queue a poll while messages are processing.
Updated status method to return concurrency and polling status
[ ] Add a new timeout value option for the amount of time to wait when the concurrent count has been reached (currently this is the normal timeout count, which may be wrong for some users)
[ ] Add unit/integration tests
[ ] Check that this works in the real world with a canary release (while still in PR)
[ ] Our users don't have concurrency right now, how might this affect them? This is most likely a breaking change any way, but we should check that there are no negative effects.