axum

Axum is the most popular web library out there, and sqlx the most popular sql library. Together they look something like this: https://github.com/tokio-rs/axum/blob/main/examples%2Fsqlx-p...

> Not much polars can do about that in Rust I'm ignorant about the exact situation in Polars, but it seems like this is the same problem that web frameworks have to handle to enable registering arbitrary functions, and they generally do it with a FromRequest trait and macros that implement it for functions of up to N arguments. I'm curious if there are were attempts that failed for something like FromDataframe to enable at least |c: Col<i32>("a"), c2: Col<f64>("b")| {...} https://github.com/tokio-rs/axum/blob/86868de80e0b3716d9ef39... https://github.com/tokio-rs/axum/blob/86868de80e0b3716d9ef39...

I really hope guide-level docs are on the roadmap for Axum. The current situation of "here are some (third-party) blog posts and YouTube videos" is not greatly encouraging. For reference: https://github.com/tokio-rs/axum?tab=readme-ov-file#getting-... https://github.com/tokio-rs/axum/blob/main/ECOSYSTEM.md#tuto...

After I read a bit about axum [1], it says it's a relatively thin wrapper on top of hyper [2], a fast and correct HTTP library. In other words, what can be done with NGINX, it can be achieved with axum (assuming you know Rust). It looks interesting, I'm not going to lie! [1] https://github.com/tokio-rs/axum [2] https://crates.io/crates/hyper

My backend for a simple web application I'm working on is entirely in Rust. Highlights: - axum: web application framework - https://github.com/tokio-rs/axum - axum-htmx: axum extractors, responders, guards for htmx - https://github.com/robertwayne/axum-htmx - rusqlite: SQLite bindings - https://github.com/rusqlite/rusqlite - maud: HTML templating as a macro - https://maud.lambda.xyz The way maud lets you compose markup works very nicely with htmx. The HX-Request header lets you know if the request is coming from htmx or if it is a regular request. You either call the top-level function if it's a regular request to get the entire page rendered, or call a subset of functions to get the appropriate partial rendered if it's an htmx request. It's also nice to easily have tests for the rendered pages. My unit tests cover verification of the ren

For completion here is the compilation time for a small project from the axum/examples[0] (125 LoC), also comparing nightly dev vs adding cranelift + mold: $ time cargo build Compiling example-todos v0.1.0 (/home/user/ws/rust/example-todos) Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.65s cargo build 1.49s user 0.58s system 123% cpu 1.685 total Compiling example-todos v0.1.0 (/home/user/ws/rust/example-todos) Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.55s cargo build 0.47s user 0.13s system 102% cpu 0.590 total [0] https://github.com/tokio-rs/axum/tree/main/examples/todos

I am not completely sure, but I think pretty much all frameworks in Rust have complex dependencies and codebase not optimized for fast compile times. You could check out Axum [1], at the first glance seems similar to actix [2]. Both use tokio which is by itself pretty big I think. Folks at makepad poured enormous effort in keeping dependency graph minimal. [1] https://github.com/tokio-rs/axum/ [2] https://github.com/actix/actix-web/

I’m referring to things like println, which isn’t a macro in any other language. If you want to stick with the serde example, then look at the diy name mangling in the deserializer trait: https://docs.rs/serde/latest/serde/trait.Deserializer.html Or the copy and pasting in Axum: https://github.com/tokio-rs/axum/blob/24f0f3eae8054c7a495cd3...

On the backend it's probably axum and tokio https://github.com/tokio-rs/axum https://tokio.rs/tokio/tutorial

https://github.com/tokio-rs/axum/pull/1346 Also for ref :)

You may also want to check out https://github.com/tokio-rs/axum if actix-web doesn't click for you.

> Oh and that type never "gets bigger" in a way that would cause compile-time explosions. FWIW Axum did get hit by last year's "huge types" regression, the maintainer opted to bypass the issue by boxing routes internally: https://github.com/tokio-rs/axum/pull/404 Which is not really surprising, as it's built on tower, which at the time Lime noted was affected: https://fasterthanli.me/articles/why-is-my-rust-build-so-slo... > ...I didn't actually trust warp that much. It's perfectly fine! It just.. has a tendency to make for very very long types, like the one we see above. Just like tower.

Maybe not with Actix, but certainly with axum: https://github.com/tokio-rs/axum Salvo is also great: https://salvo.rs

- Actix Web https://github.com/actix/actix-web - Axum https://github.com/tokio-rs/axum (what I'm currently using in production) - Hyper https://github.com/hyperium/hyper Positive experiences mostly. If it builds, it'll usually run with no issues. Ecosystem is mature enough for large production apps.