SQS Workers
SQS Workers gives the ability to process messages off an SQS queue using multiple worker threads. It uses python multithreading to optimize CPU usage since a good portion of time is spent requesting messages and polling the SQS queue. It can be used similarly to an AWS Lambda which cannot (as of right now) be used in conjunction with SQS.
Versions
- :: 1.2 - support for bulk processing
1.1 - revert to best known working version 0.1.12 0.2.0 - rewrite implemention on top of concurrent.futures; adds tests 0.1.13 - support bulk message processor 0.1.12 - adding exception handler 0.1.11 - customize queue polling 0.1.10 - increase to max wait time for polling 0.1.9 - get messageattributenames 0.1.8 - tweaks for public pypi 0.1.7 - bugfix for thread naming 0.1.6 - bugfix for emptry sentry client 0.1.5 - bugfix for pip install 0.1.4 - support for elasticmq 0.1.2 - initial version
Usage
A basic call to SQS Workers would look like this:
options = {
'sqs_session': sqs_session,
'queue_name': 'ddev-test-queue',
'sqs_resource': sqs_resource,
'MessageProcessor': MsgProcessor,
'logger': msg_logger,
'statsd': statsd,
'sentry': None,
'worker_limit': 1
}
c = Crew(**options)
A basic call to SQS Workers for Bulk Processing would look like this:
options = {
'sqs_session': sqs_session,
'queue_name': 'ddev-test-queue',
'sqs_resource': sqs_resource,
'MessageProcessor': MsgProcessor,
'logger': msg_logger,
'statsd': statsd,
'sentry': None,
'worker_limit': 1,
'bulk_mode': True
}
c = Crew(**options)
Installation
Add SQS Workers to your package dependencies
requirements.txt
sqsworkers
And then install using pip pip install -r requirements.txt
Tests
Make sure tests pass: pytest tests/test_crew.py
Contributors
Pull requests, issues and comments welcome. For pull requests:
Add tests for new features and bug fixes
Follow the existing style
Separate unrelated changes into multiple pull requests
See the existing issues for things to start contributing.
For bigger changes, make sure you start a discussion first by creating an issue and explaining the intended change.
Atlassian requires contributors to sign a Contributor License Agreement, known as a CLA. This serves as a record stating that the contributor is entitled to contribute the code/documentation/translation to the project and is willing to have it used in distributions and derivative works (or is willing to transfer ownership).
Prior to accepting your contributions we ask that you please follow the appropriate link below to digitally sign the CLA. The Corporate CLA is for those who are contributing as a member of an organization and the individual CLA is for those contributing as an individual.
License
Copyright (c) 2017 Atlassian and others. Apache 2.0 licensed, see LICENSE file.
Metadata
Release files for sqsworkers 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sqsworkers-1.2.tar.gz | 5.9 kB | Without provenance | Details |
Release files / sqsworkers-1.2.tar.gz
| Download URL | sqsworkers-1.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
311f900918e196019bf96b19b9c0a51cf13b0a7a133bfbf3a21570334507c6fd
|
|
BLAKE2b-256 checksum How to use checksums |
79cab4ed3e2b71649c4b4c8d920d156963fe4cd3760c55738552d0d76f363850
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.4.1 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.4
|
Security for sqsworkers 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.