Editor’s note: This post was updated on 21 April 2023 to add Axum and warp to the list of frontend web frameworks and update our considerations about the maturity of some of the previously mentioned frameworks. This update also includes a comparison of the most popular Rust web frameworks.
Rust is one of the most popular languages for developers because of its open source, fast, reliable, and high-performance features. When building a new API in Rust, it is important to consider the benefits and drawbacks of web frameworks for both frontend and backend development.
In this article, we will discuss what a web framework is and provide recommendations for which frameworks to use for Rust in frontend and backend development. Let’s get started.
A web framework is a software tool that supports the development of web applications; a web framework can range from a small codebase for micro apps to a large codebase for enterprise apps and everything in between. The most extensive web frameworks provide libraries of support for databases, templating, sessions, migration, and other utilities to speed up the development process. More simplistic frameworks focus more acutely on frontend management for static content rendering.
Whatever your project needs, web frameworks can provide the web services, web resources, and web APIs that development teams need to help bring their ideas to life. When choosing the appropriate web framework for your project, your development team should consider the relative importance of the following:
Depending on your project’s priorities, different web frameworks will help you address your most pressing development requirements. In this article, we will specifically discuss frameworks built with Rust.
Web frameworks make web development and building desktop applications easier for developers. By standardizing the building process and automating common activities and tasks, web frameworks can save developers time and even promote reusing code to increase efficiency.
In the following sections, we will review web frameworks in Rust as they pertain to both frontend and backend development. We will then look into each framework’s phase in terms of stability, production readiness, and project size.
WebAssembly (Wasm) is a type of coding in low-level languages that can be run in modern web browsers. It supports C/C++, C#, Go, and Rust, with a target compilation for byte code so it can be run on the web with nearly-native performance. Wasm output is run alongside JavaScript and can be published to npm and other packages.
Rust uses a tool called wasm-pack to assemble and package crates that target Wasm. To learn more about Wasm and Rust, check out our guide to getting started with WebAssembly and Rust.
Stdweb is a frontend standard library that gives Rust the power to communicate directly with JavaScript web APIs. It was crafted to give developers the power to create full-fledged JavaScript apps in Rust by providing easy API binding between the languages to improve speed and performance.
Stdweb supports closures, arbitrary structure, and the standard components of web APIs, including DOM, events, and windows. Here’s a link to a few sample projects to get a grasp of how it works.
Yew is an improved version of stdweb. It is a component-based framework similar to React and Elm, with support for multi-threading, component-based patterns, and other features similar to stdweb.
Percy is a toolkit developed for building single-page apps (SPAs) and managing UI, including optimization for specific browsers and screen sizes (desktop and mobile). Percy is still a work in progress; improvements are needed for better structure, optimal boilerplate, and general bug fixes.
Sauron is a micro frontend framework that was inspired by The Elm Architecture. It has support for events, state management, and components. Sauron uses a library called html2sauron to convert HTML into Sauron view code for rendering optimization.
Dioxus is a UI library elegantly designed to be React-like — it’s built around a virtual DOM to support building cross-platform apps for web, mobile, and desktop. It has support for component-based architecture, concurrency and async, props, an inbuilt error handler, state management, and more.
Iced is a GUI library for cross-platform development. It’s structured in Elm style and supports reactive programming, inbuilt widgets, and async while also having a modular/reusable component-based architecture with type safety and simplicity.
Tauri is a Rust library built as a light JavaScript framework for building desktop applications with the integration of any frontend technology that renders HTML, CSS, and JavaScript into your web view for its UI.
For the best documentation and impressive support for interpolation with JavaScript, I suggest your selection should be determined by your specific use case, library stability, and the listed production readiness for each framework above.
Backend development refers to the server-side operation of a web app. It also describes the core operations of an app that usually controls and handles its data and actions, such as submitting a form or logging into a web account. Backend development focuses primarily on data management and the database, scripting, automation, and architecture necessary to handle it. Some of the most common features of a typical backend development framework include:
Rust provides various web frameworks for backend development, including a combination of tools, helpers, and libraries from different vendors that are each designed to provide a way to build, test, and run apps with efficiency, security, and flexibility.
Rocket is a popular web framework that makes it easy for developers to write fast web apps without skimping on security, flexibility, or function. It has support for testing libraries, cookies, streams, routes, templates, databases, ORMs, boilerplates, and more. Rocket also has a large and active developer community.
Like Rocket, Actix is another powerful backend web framework. Actix features an architectural pattern based on Rust’s actor system and is well-equipped for building writing services and micro apps. It has support for routing, middleware, testing, WebSockets, databases, and automatic server reloading, and can be hosted on Nginx. Actix can be used to build a full-scale web app and API.
Axum is a web framework that focuses on providing a foundation for building asynchronous, scalable, and maintainable web applications. It was designed with the needs of modern web services in mind, including support for HTTP/2, WebSockets, and other modern protocols.
It was built on Tokio, Tower, and Hyper, which in hindsight, used the libraries for middleware, services, etc.
Warp is designed to be fast, lightweight, and composable, making it ideal for building high-performance web services and APIs.
Gotham is a flexible web framework built for stable Rust that promotes “stability, safety, security, and speed.” It is statically typed, ensuring the application is always correctly expressed at compile time. Gotham provides async support with the help of Tokio and hyper.
Gotham supports routing, extractors (type-safe data requests), middleware, state sharing, and testing. Gotham does not have structure, boilerplate, or database support.
Rouille is a microweb framework that employs a linear request and response design via a listening socket that parses HTTP requests. It is built to be easy to learn for Rust users. Rouille has support for requests through CGI, input (request header and body), content-encoding, proxy, sessions, and WebSockets.
Thruster is a fast and reliable Rust web framework inspired by the layering and design of Koa and Express.js. It is SSL-ready, secure, intuitive, and testable. Thruster is built to accommodate async/await and provides support for middleware, error handling, databases, and testing.
Tide is a minimal framework similar to Express.js (Node.js), Sinatra (Ruby), and Flask (Python) for rapid development that promotes building web apps in asynchronous versions. Tide provides support for routing, auth, listener, log, template engines, middleware, testing, and other utilities.
Dropshot is a simple and lightweight server-side library for creating REST APIs. It has support for openAPI specs, async, and logging
For building advanced web apps, I recommend Rocket, Actix, Axum, warp, and Tide (for asynchronous support) to roll your backend. They each offer a sizable support library and have the largest communities in comparison to other frameworks. They are also well-liked in the Rust community.
Actix, Rocket, Axum, and warp are all popular web frameworks for Rust, each with their own unique features and strengths. Here’s a closer look at the commonalities found for each of them:
| Features | Explanation | Actix | Rocket | Axum | warp |
|---|---|---|---|---|---|
| Async/await support | Actix, Rocket, Axum, and warp all use Rust’s async/await syntax to provide non-blocking I/O operations for web applications. This allows for better performance and scalability, as the framework can handle multiple requests simultaneously without blocking or slowing down. | ✅ | ✅ | ✅ | ✅ |
| Middleware | Middleware is a common feature in web frameworks that allows developers to add functionality to the request-response cycle, such as logging, authentication, and error handling. All of the most popular Rust web frameworks – Actix, Rocket, Tide, and warp – support middleware. | ✅ | ✅ | ✅ | ✅ |
| WebSockets support | They all support WebSocket but the specific syntax and features for working with WebSockets may vary across the frameworks, so the choice of framework will depend on the specific needs of the project. | ✅ | ✅ | ✅ | ✅ |
| Concurrerncy & Performance | Actix and Axum may be better suited for applications that require high levels of concurrency and performance, while Rocket and warp may be better suited for applications that prioritize ease of use and flexibility. | ✅ | 🚫 | ✅ | 🚫 |
| Cookie and session | Cookies and sessions are important components of many web applications, allowing developers to store and retrieve data that is associated with a specific user or client | ✅ | ✅ | ✅ | ✅ |
| Community growth size | All four web frameworks have active communities and are continuing to grow in popularity. Actix and Rocket are more established frameworks and have larger communities, while Axum and warp are newer but still have growing communities of users. | ✅ | ✅ | ✅ | ✅ |
The majority of Rust web frameworks all have minor releases but still are used largely in production by the community. Having said this, when choosing the correct web framework for your frontend or backend development project, it is important to consider what the framework’s community support and growth is like, the stability of the framework, if it is production-ready, and whether it is right for the size of your project. Depending on your answers, you will be on your way to using web frameworks to improve efficiency, speed, and productivity in Rust.
Debugging Rust applications can be difficult, especially when users experience issues that are hard to reproduce. If you’re interested in monitoring and tracking the performance of your Rust apps, automatically surfacing errors, and tracking slow network requests and load time, try LogRocket.
LogRocket is like a DVR for web and mobile apps, recording literally everything that happens on your Rust application. Instead of guessing why problems happen, you can aggregate and report on what state your application was in when an issue occurred. LogRocket also monitors your app’s performance, reporting metrics like client CPU load, client memory usage, and more.
Modernize how you debug your Rust apps — start monitoring for free.
Nushell is a modern, performant, extensible shell built with Rust. Explore its pros, cons, and how to install and get started with it.
The Zed code editor sets itself apart with its lightning-fast performance and cutting-edge collaborative features.
Infinite scrolling in Next.js no longer requires external libraries — Server Actions let us fetch initial data directly on the server.
Create a dynamic demo blog site using Django and React to demonstrate Django’s server-side functionalities and React’s interactive UI.
14 Replies to "Exploring the top Rust web frameworks"
Let’s not forget dropshot by oxide computer company.
No Warp?
Yeah, you’re missing Warp, it’s the Tokio equivalent to Tide. Warp and Tide are both quite good, it just depends on whether you favor async-std or tokio.
Also, I think Iced deserves a mention here, since it can compile to WebAssembly and WebGPU, in addition to platform-native Metal, Vulkan, and OpenGL. Also, people are even experimenting pairing Iced with cargo-mobile, which is also exciting!
+1 to this
warp and (warp-based) rweb definitely are missing from the overview
How can you say Rocket is production-ready when it can’t even compile with stable Rust? In my environment, I will have to wait until there’s a release that can run on stable Rust. Hopefully it’s coming soon with Rocket v0.5.
> Rocket is a popular, mature web framework
Latest Release: 0.5.0
As long as it hasn’t reached 1.0, you can’t really call it mature, now can you? It’s an admission from the developers themselves that they have not implemented everything on the roadmap yet.
Sauron isn’t outdated. It is still being actively developed. Seed is effectively dead, and Yew’s syntax and performance are vastly inferior to it. By far the best frontend web framework at the moment.
Why do you say that? By Github stats, both Sauron and Seed went on life support six months ago, like Stdweb and Percy did a year ago. Only Yew is maintaining its velocity and only Smithy looks dead.
Axum is missing 🙂
friendly explained
Hi, it appears you’ve updated the article, and yet you list warp and axum as being not “production-ready”. You never explain your criteria for this subjective determination, but you also list warp as not supporting either concurrency or async-await, and axum as not supporting async-await, and yet, I’m literally doing that here:
https://github.com/diba-io/carbonado-node/blob/cb134b57c260d48a405fbd2199c3201468e1259e/src/frontend/http.rs
So, these specific claims are objectively false.
As for the “production-readiness” of frontend frameworks, Iced is used by System76 for their new desktop software on Pop!_OS, which is a very popular operating system that they ship on millions of dollars worth of hardware. See:
https://www.phoronix.com/news/COSMIC-Desktop-Iced-Toolkit
Dioxus and Tauri are also making leaps and bounds of progress, and there’s a big effort towards the modernization of Yew as well. If anyone wants my recommendation, well, it depends on the use-case, but I’d recommend looking into Dioxus, Axum, and Tauri. Iced is also a very capable UI library, but I don’t think it’s as good in web contexts anymore. Rust is actually a very flexible language, and WebAssembly support has come a long way.
Really, this article just isn’t going to age well. You should probably remove it, or add a big huge giant disclaimer, “These are just my opinions and I don’t actually know very much about what I’m writing about at all lololol”. Otherwise you’re just providing disinformation on what’s likely a prominent search engine query, and will continue to do so as the ecosystem matures.
I appreciate the feedback and I can understand why you may feel that way.
Regarding the production readiness of certain Rust frameworks, I must clarify that it is not my intention to discredit any framework or library in the Rust ecosystem.
However, it is important to note that the criteria for production readiness can be subjective and depend on a variety of factors, such as community support, stability, performance, and security. In the article, I may have overlooked certain factors or not provided enough context for why I came to the conclusion that a particular framework may not be production ready.
I would update the article by buttressing more on the criteria to which the frameworks are ready for production and as well add some of the companies that use each one of them.
Once again, I appreciate your feedback and will use it to improve the quality of my content going forward.
I do agree with the poster that I was confused by the parts regarding Axum not having async support when Axum is an async framework built on top of Tokio, the rust async runtime, as mentioned in the article.