sqlite_modern_cpp
litequeue
Our great sponsors
| sqlite_modern_cpp | litequeue | |
|---|---|---|
| 1 | 3 | |
| 854 | 138 | |
| 1.3% | 9.4% | |
| 4.4 | 7.4 | |
| 5 months ago | about 2 months ago | |
| C++ | Python | |
| MIT License | 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.
sqlite_modern_cpp
-
What's New in SQLite 3.35
I just wrote something using https://github.com/SqliteModernCpp/sqlite_modern_cpp, which I chose after 10 minutes of searching around. Should I have used yours instead? How should I decide?
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
What are some alternatives?
sqlite_orm - ❤️ SQLite ORM light header only library for modern C++
datasette-dateutil - dateutil functions for Datasette
soci - Official repository of the SOCI - The C++ Database Access Library
pgjobq - Atomic low latency job queues running on Postgres
LMDB - Read-only mirror of official repo on openldap.org. Issues and pull requests here are ignored. Use OpenLDAP ITS for issues.
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication
SQLite - Unofficial git mirror of SQLite sources (see link for build instructions)
litestream - Streaming replication for SQLite.
ObjectBox C/C++ database - C and C++ database for objects and structs
starqueue
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
datasette.io - The official project website for Datasette