litequeue
tembo
| litequeue | tembo | |
|---|---|---|
| 3 | 4 | |
| 138 | 657 | |
| 3.6% | 18.4% | |
| 7.4 | 9.8 | |
| about 2 months ago | 1 day ago | |
| Python | Rust | |
| MIT License | PostgreSQL License |
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.
litequeue
-
Choose Postgres Queue Technology
To make sure you that the message you are trying to retrieve hasn't been locked already by another worker.
[0]: https://github.com/litements/litequeue/
[1]: https://github.com/litements/litequeue/blob/3fece7aa9e9a31e4...
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
SQLite is missing some features like `SELECT FOR UPDATE`, but you can work around some issues with a few extra queries. I wrote litequeue[0] with this specific purpose. I haven't been able to use it a lot, so I don't have real-world numbers of how it scales, but the scaling limits depend on how fast you can insert into the database.
[0]: https://github.com/litements/litequeue
-
What's New in SQLite 3.35
The `RETURNING` is so awesome! I'm implementing a set of data structures on top of SQLite, one of them is a queue[0], and I had to do a transaction to lock a message and then return it, but this makes it easier.
There's one little issue I keep finding with SQLite, and it's that most virtual servers / VM images ship with version 3.22.0, and upgrading often means building from source.
In any case, SQLite is absolutely wonderful. My favorite way of building products is having a folder for all the DBs that I mount to docker-compose. This release makes it even better.
[0] https://github.com/litements/litequeue
tembo
-
Tembo Operator: a Rust-Based Kubernetes Operator for Postgres
Stacks[1] are basically recipes for deploying Postgres for specific use cases. This includes extensions, Postgres configs and application deployments (example: PostgREST)
For examples, you can look at https://github.com/tembo-io/tembo/tree/main/tembo-operator/s...
[1] Blog about Stacks: https://tembo.io/blog/tembo-stacks-intro/
- Show HN: One Postgres message queue to rule them all
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
Perhaps you mean https://github.com/CoreDB-io/coredb/tree/main/extensions/pgm...
Your link results in a 404.
What are some alternatives?
datasette-dateutil - dateutil functions for Datasette
neoq - Queue-agnostic background job library for Go, with a pleasant API and powerful features.
pgjobq - Atomic low latency job queues running on Postgres
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication
starqueue
sqlite_modern_cpp - The C++14 wrapper around sqlite library
tqs - Tiny Queue Service (Server)
litestream - Streaming replication for SQLite.
pgtt - PostgreSQL extension to create, manage and use Oracle-style Global Temporary Tables and the others RDBMS
Suwayomi-Server - A rewrite of Tachiyomi for the Desktop