Tide VS Gotham

Rust has several, production ready, REST API frame works.

Rust allows me to mainly only run the application to confirm things work from a business perspective.

For people starting out building stuff in rust - understand that there is a distinction of async code and libraries and can lead to confusing compiler errors if you don't realize there is a distinction. It's simple in hindsight but did cause me to waste hours barking up the wrong trees at first. Other wise just learn about `match` and Result/Option types asap, they're fundamental.

https://github.com/http-rs/tide tide is great to create an http server / routes

https://github.com/djc/askama I use this to template out HTML and it checks all my boxes, dynamic data, passing in functions, control flow.

https://github.com/launchbadge/sqlx sql interface for a variety of backend, async safe.

https://github.com/seanmonstar/reqwest http client to make requests

Rust is amazing, don't let the initial few speed bumps discourage you - building real things with rust is no more challenging today than any other modern language stack.

https://crates.io/crates/salvo - 581k all time and peak daily of ~2750 in last few months https://crates.io/crates/rocket - 2.68mil all-time / ~6200 daily https://crates.io/crates/actix-web - 9.8mil all-time / ~21k daily https://crates.io/crates/axum - 8.8mil all-time / 64k daily https://crates.io/crates/warp - 7.9mil all-time and 19k daily https://crates.io/crates/tide - 886k all-time / 2250 daily

Hi, guys, how you doing? I'm trying out this web framework Tide just to make a toy project and learn more about Rust. The create_payment_handler function is called by the framework whenever there is a POST request to /payment/ containing a JSON body with the payment information.

tide

I'm developing the backend of https://www.cozydate.com/ in Rust. Async Rust is not productive yet, so I tried rouille http server which lets me write non-async request handlers. Unfortunately, it uses an unbounded thread pool and falls down under load https://github.com/tiny-http/tiny-http/issues/221 . Then I tried Tide and a threadpool to call my non-async API handlers. This worked, but was really ugly, and I had issues with uploads after deploying to Heroku https://github.com/http-rs/tide/issues/878 .

You could also habe a look at tide apparently it is stable and production ready.

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