Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
sqlx
🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite. (by launchbadge)
Doesn't look like it. There's mention of it here but it was closed in favour of the ticket I linked before, (which was then closed).
Sure, it is this crate here https://github.com/JordiPolo/minos/tree/master/crates/daedalus Also I run `cargo test` from the crate root here, the parent project does not have tests :D
My first try was with flume, which uses a single producer, multi-consumer setup, and while it compiles and runs, it's magnitudes slower than the serial version. Here's a psuedocode rendition:
If you are interested, you can follow the RFC for const trait impls (tracking issue | RFC).
The raw data is here. Or you could just manually bisect it and try to install various dates until you get what you want.
Most projects are using https://docs.rs, so it's not too common to publish yourself. There are a few options:
I'm partial to sqlx or diesel, but your SQL layer depends on whether you want/have async, your actual backend database, if you want an ORM or not, and how concurrent you need access to be.
Using the tower crate's rate-limiting middleware as suggested by this issue. I think would work fine if I cloned and passed the wrapper around. But I had type-checking issues trying to stash the rate-limited reqwest Client in a global variable, as the type contains a closure: RateLimit>>.