sabledb
rq
| sabledb | rq | |
|---|---|---|
| 4 | 27 | |
| 380 | 9,547 | |
| - | 1.0% | |
| 9.4 | 8.6 | |
| 5 days ago | 7 days ago | |
| Rust | Python | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sabledb
-
Redis Re-Implemented with SQLite
I switched from SSDB to Kvrocks recently, because SSDB is abandoned and the author missing for 3 years now. I used to recommend SSDB, but now there's better alternatives available:
https://github.com/apache/kvrocks
https://github.com/sabledb-io/sabledb
-
SableDb – a key/value store that uses RocksDB and Redis API (written in Rust)
Not that I see?
https://github.com/sabledb-io/sabledb/blob/main/sabledb/src/...
- SableDB: Open-source, persistent, Redis-compatible db written in Rust
rq
-
Redis Re-Implemented with SQLite
That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?
https://python-rq.org -
The Many Problems with Celery
https://github.com/rq/rq is to the rescue.
-
Keep the Monolith, but Split the Workloads
We use RQ[0], it has Redis as a dependency. It’s pretty straightforward and we’re very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.
[0] https://python-rq.org/
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.
Moved to Python-RQ [1] + Redis and been rock solid for years now.
[1] https://python-rq.org/
- Ask HN: Redis Queue Hacks and Questions
- What libraries do you use the most alongside django?
-
Recommendations other than celery to send an API processing in background, which would only take 5 mins to process and API usage would be once a month or so.
Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq
-
GPU instance crashes when two python processes use the same pt file
We have a GPU (G5) instance that uses Python RQ (https://python-rq.org/).
- Dynamically update periodic tasks in Celery and Django
- Celery + RabbitMQ alternatives
What are some alternatives?
Sidekiq - Simple, efficient background processing for Ruby
celery - Distributed Task Queue (development branch)
go-sqlite3 - sqlite3 driver for go using database/sql
huey - a little task queue for python
sled - the champagne of beta embedded databases
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
redimo.go - Use the power of DynamoDB with the ease of the Redis API
mrq - Mr. Queue - A distributed worker task queue in Python using Redis & gevent
Memcached - memcached development tree
procrastinate - PostgreSQL-based Task Queue for Python
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
Apache Kafka - Mirror of Apache Kafka