Tide VS axum

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.

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

Moreover, I especially like where Rust is right now in the web space. It really feels like there’s a lot of smart people working on the next generation of web development tools - it feels like the place to be. There are a range of great open-source web dev tools that are just reaching critical levels of maturity. Axum, which I used to build Prodzilla, feels ready for out of the box web dev, and is crazy-performant, as I write about later. More recently available is Loco, a Rails-like framework for building web applications in Rust that's picking up steam. And in dev-tooling and hosting there’s Shuttle, a 1-line hosting solution for Rust backends.

CryptoFlow is a full-stack web application built with Axum and SvelteKit. It's a Q&A system tailored towards the world of cryptocurrency!

You also get to specify the accepted HTTP method of the URL via axum::routing. To answer its name, modularity, Axum also supports nested routes as we'll see later in this series. Next is the layer, a method used to apply tower::Layer to all routes before it. This means that routes added after the layer method will not have such a layer applied to their requests. In our case, we used the layer to add tracing to all HTTP requests and responses to our routes. This is needed for proper logging. The tower_http::trace::TraceLayer can even be really customised.

I build simple rust axum api server with Prisma client rust. This is my something done with rust and I really enjoyed rust!

In this article we'll take a comprehensive look at how to use Axum to write a web service. This will also include the 0.7 changes.

You have a couple of options for the underlying web framework to pair with Leptos: Axum or Actix. Axum seems to carry more favour currently, so we start with that. Assuming you already have Rust set up on your system:

I’m the author of https://kellnr.io. When I started working on Kellnr three years ago, https://rocket.rs was “the web framework” to use. Unfortunately, the project seems dead. Before adding more functionality using an unmaintained framework, I want to port Kellnr to https://github.com/tokio-rs/axum.

Web Framework : axum.