litequeue
datasette-dateutil
| litequeue | datasette-dateutil | |
|---|---|---|
| 3 | 1 | |
| 138 | 7 | |
| 3.6% | - | |
| 7.4 | 3.6 | |
| about 2 months ago | about 2 years ago | |
| Python | Python | |
| MIT 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
datasette-dateutil
-
What's New in SQLite 3.35
Hah, yeah PST v.s. PDT does make this harder.
At that point I'd switch to using additional custom SQL functions. I wrote a plugin called datasette-dateutil https://datasette.io/plugins/datasette-dateutil that exposes some extra functions, but it doesn't have anything useful for timezone calculations yet.
I've opened an issue: https://github.com/simonw/datasette-dateutil/issues/4
What are some alternatives?
pgjobq - Atomic low latency job queues running on Postgres
datasette-dashboards - Datasette plugin providing data dashboards from metadata
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication
litestream - Streaming replication for SQLite.
sqlite_modern_cpp - The C++14 wrapper around sqlite library
datasette.io - The official project website for Datasette
starqueue
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
rqlite - The lightweight, distributed relational database built on SQLite.