todo_rotomy
kerkour.com
Our great sponsors
| todo_rotomy | kerkour.com | |
|---|---|---|
| 5 | 2 | |
| 8 | 456 | |
| - | 0.7% | |
| 0.0 | 4.5 | |
| over 1 year ago | about 2 months ago | |
| Rust | Rust | |
| - | Apache License 2.0 |
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.
todo_rotomy
-
SQL and Rust
To check, if it meets your use case see the todo example or guide.
-
Recommended data access patterns for Rust?
Sound like object-relational mapping. I'm the author of the Toql ORM, see a Todo example here. I've tried hard to make the API simple, but the lib is fairly capable. I'm using it to power a big REST-server for online-exams (~60 tables). It's currently for MySQL only, more next year.
-
Toql 0.4
Good question! Frankly, I have never really worked with SeaORM and only played around with diesel. If I compare the two Todo examples with SeaORM and Toql I see that Toql works with "normal" structs and the code is more slick for my taste whereas SeaORM works with model structs, a somehow more classical approach. Maybe someone with SeaORM experience can say more about this.
-
[ANN] Toql - A friendly and productive ORM
So check out crates.io, the guide or the Todo example.
kerkour.com
-
SQL and Rust
There are plenty: - diesel - famous example of what the Rust type system can get you beyond just "memory safety". My go-to choice for most projects. Having autocomplete for my database DSL is something I find it hard to go without. But it comes at a fairly high cost of confusing, generic-heavy code. - sqlx - also a very solid choice. You write SQL queries, which are optionally checked against a database instance at compile-time. A downside I've heard repeated a lot (by some fairly reputably figures) is that sqlx adds a fairly significant overhead to queries, and according to this issue is 7-70x slower than diesel. If the performance of your database is important to you, run some benchmarks and see if it's an issue - seaorm - a relatively new ORM, and I haven't used it much, but my initial impressions were that it was a little too "magic". Maybe it just reminded me too much of Spring Boot. I'm not sure. It's probably a totally fine library - postgres (or equivalent) - you can always just skip the ORM and use the database driver directly. Pretty nice for smaller projects, but totally viable for big projects too. Just a matter of personal preference
-
How to implement worker pools in Rust
As usual, you can find the code on GitHub: github.com/skerkour/kerkour.com (please don't forget to star the repo 🙏).
What are some alternatives?
sea-orm - 🐚 An async & dynamic ORM for Rust
shisho - Lightweight static analyzer for several programming languages
toql - A friendly and productive ORM
binserve - A fast production-ready static web server with TLS (HTTPS), routing, hot reloading, caching, templating, and security in a single-binary you can set up with zero code.
diesel - A safe, extensible ORM and Query Builder for Rust
sandwich - Sandwich is a multi-platform, multi-language, open-source library that provides a simple unified API for developers to use (multiple) cryptographic libraries in their applications.
metrics
tangram - Tangram makes it easy for programmers to train, deploy, and monitor machine learning models.
myblog - Personal blog written in Rust, using salvo and sqlx
hypercube - HyperCube is a revolutionary, high-performance decentralized computing platform. HyperCube has powerful computing capabilities to provide high-performance computing power and large-scale data storage support for VR, AR, Metaverse, Artificial Intelligence, Big Data, and Financial Applications.🛰
tangram - Tangram is an all-in-one automated machine learning framework. [Moved to: https://github.com/tangramdotdev/tangram]