SimpleQ

A simple, infinitely scalable, SQS based queue.

Purpose

As I've been developing large scale web applications in Python for several years, I've come to try all of the available queueing solutions, namely Celery and RQ.

What I love about Celery is that it supports many backends, and is extremely configurable. Celery is great for large projects where you need to support very specific queueing requirements, and have lots of time to spend configuring and optimizing your software.

On the other end of the spectrum is RQ -- RQ is a very simple, minimalistic, queueing system which exclusively works with Redis. I love RQ because it can be dropped into any Python project in a number of minutes, and requires very little configuration. It also ships with a great dashboard and utilities.

Now the downsides.

As I've built more and more software over the years, I've come to really appreciate Amazon SQS (Simple Queue Service). Not only is it incredibly fast and available in all of the AWS Regions, but it's the cheapest possible queueing system (in terms of hosting costs) by a huge margin, it requires 0 setup and configuration (other than having an AWS account), and almost never goes down.

What I really want to use is a simple queue system like RQ, that exclusively runs on SQS and is optimized for speed and cost. This means a queue system that will properly handle batching messages (my main issue with Celery is that it does not support this) and require minimal configuration.

My goal with SimpleQ is to build the queueing system I've always wanted: a simple SQS based queue that is extremely stable, fast, and cost effective.

Documentation

This project's documentation is hosted at ReadTheDocs, for all usage and setup information you'll want to follow this link: http://simpleq.readthedocs.org/en/latest

-Randall

You might also like...

Comments

[Snyk] Fix for 2 vulnerabilities
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed

By pinning:

Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- | 539/1000
Why? Has a fix available, CVSS 6.5 | Arbitrary Code Execution
SNYK-PYTHON-BOTO-40479 | boto:
2.30.0 -> 2.39.0
| No | No Known Exploit | 536/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 4.3 | Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PY-1049546 | py:
1.4.20 -> 1.10.0
| No | Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information: 🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic
opened by snyk-bot 0