Gotham VS Iron

Gotham Gotham, Rust's flexible web framework, is a trustworthy ally for developers looking for safety, security, and extensibility in their web applications. Gotham provides developers with a solid foundation for building secure and efficient web solutions, thanks to its powerful routing system and support for asynchronous request handling. Gotham helps developers avoid common pitfalls and ensures code integrity by prioritizing safety. Its extensible design makes it simple for developers to customize and enhance their applications, making Gotham an excellent choice for projects requiring flexibility and a focus on security.

If one were to undertake a project of developing something like this, which is the best web framework for it. I did some cursory research and discovered these back-end frameworks - actix, axum, poem, salvo, warp, gotham and rocket.

I don't have a big preference. I really like warp, I really like Axum, other frameworks look really nice so maybe I'll try those one day. Gotham is on my list, it looks really cool!

Why not? I recently removed chrono from gotham.

Gotham

I've written many things using Iron and it's been fine. It's not particularly developed any more but I am not aware of any major outstanding issues.

I don't miss the time when we basically only had Iron

iron

There're many web framework in rust, such as SergioBenitez/Rocket , actix/actix-web ,poem-web/poem , iron/iron . How do I chiose, anyone suggestion？

I'm not sure which definition of backend you are thinking of here. In case you simply mean "server side", here are a couple of libraries that might be of use: iron - been a while since I used it, used it for a couple smaller projects rocket (nightly only) - no personal experience, but a lot of people seem to like it diesel - a bit complex to wrap your head around, but once you get the idea it's really nice. Definitely check out the examples.

it's taken by a web framework https://github.com/iron/iron

Your comment touches on a few misconceptions I see a lot.

Firstly, `reqwest` exposes both an async and a synchronous API, allowing the developer to choose which one to use. They are largely interchangeable code-wise. [1]

Secondarily, and more broadly, async is possible to opt out of. You must understand that most web and network related libraries will be async by default for performance, because people who write in Rust and people who write web servers typically care greatly about performance. This is the intersection of those two groups. That being said, there are options outside of that ecosystem. [2]

If you truly want to use an asynchronous library without migrating your application to run entirely on an async runtime like tokio, you can run it inside of a synchronous function without much trouble. I've put together a playground link for you. [3]

1. https://docs.rs/reqwest/0.11.2/reqwest/blocking/index.html

2. Iron: https://github.com/iron/iron

There are several web frameworks for Rust: Rocket, Actix, Warp, Iron - but only Actix has released a stable 1.0 release, and there has been considerable controversy over how it uses unsafe Rust.