mosys VS axum

To find answers, we wanted to get our hands dirty with three popular Rust web frameworks including rocket, axum, and actix, and get a feeling for their performance, features, and most importantly the developer experience.

I really hope guide-level docs are on the roadmap for Axum. The current situation of "here are some (third-party) blog posts"[0] is not greatly encouraging.

[0]: https://github.com/tokio-rs/axum/blob/main/ECOSYSTEM.md#tuto...

For this example, we will use axum, a web framework that works on top of tokio.

If your lambda handles multiple endpoints of your API, the crate axum facilitates the routing within the lambda.

We’ll use Axum with Tokio to build a web backend, Tracing for logging, and Serde for serialization and deserialization.

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

If you are familiar with API development in Rust, you may recognize this syntax from Axum. This puzzling question piqued my curiosity and led me to build Cairo, where I re-implemented some key Axum concepts in a simpler way as a learning exercise. I’ve long been fascinated by the intermediate + advanced concepts library authors employ to make their interfaces feel frictionless. Rust sits in a brilliant space because of the way it melds high-level expressiveness with low-level control and performance. One of the ways it accomplishes this is using macros.

Let's create a small prototype in Rust to demonstrate the concept using Tera and Axum.

There are some proposals on how to do it already such as https://github.com/tokio-rs/axum/issues/1698.