utoipa
axum
utoipa | axum | |
---|---|---|
15 | 150 | |
1,847 | 16,204 | |
- | 2.7% | |
8.1 | 9.2 | |
9 days ago | 9 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
utoipa
-
What's everyone working on this week (23/2023)?
In case you didn't know https://github.com/juhaku/utoipa is really nice to generate openapi spec and have a swagger!
-
OpenAPI v4 Proposal
play-swagger [2] for scala + play. They generate a significant portion of your spec for you, then a client can be generated from the spec.
[1] https://github.com/juhaku/utoipa
[2] https://github.com/iheartradio/play-swagger
-
REST API in RUST with ntex
utoipa
-
Announcing utoipa 3.0.0, one year anniversary release - Compile time OpenAPI library for Rust
Latest release notes: https://github.com/juhaku/utoipa/releases/tag/utoipa-3.0.0
- New Tokio blog post: Announcing axum 0.6.0
-
Using Rust at a Startup: A Cautionary Tale
I've written a few backend APIs with rust and I have to disagree. Not only have the frameworks managed to get the ergonomics similar to your popular GC lang[0][1], the natural lack of shared mutable state of HTTP handlers means you very rarely have to encounter lifetimes and a lot of the language's advanced features. What's more, now when I go back to work with other languages, I can't help but notice the significant number of unit tests I'd not have had to write in Rust. It doesn't have a Rails and Django but it's an easy pick over anything at the language level.
A note on performance, Rust's the only langauge where I haven't had the need to update my unit test harnesses to `TRUNCATE` data base data instead of creating a separate db per test on PostgresSQL.
I'll also like to mention the gem that is SQLx[1]. As someone who's never been satisfied with ORMs, type checked SQL queries that auto-populate your custom types is revolutionary. With the error-prone langauge-SQL boundary covered, I was surprised just how good it can get making use of the builtin PostgreSQL features. Almost to the point that amount of effort the community's put to building great tools like Prisma.js and feel like a fool's errand (at least so for PosgreSQL).
[0]: https://github.com/alexpusch/rust-magic-function-params
[1]: https://github.com/juhaku/utoipa
[3]: lib.rs/crates/sqlx
-
Book Review: Zero To Production In Rust
Going to strongly disagree here. This isn't necessary in most cases. You likely do not need to test actix-web. actix-web already has more tests than you can possibly think of for exercising its correctness. So why do you need to black-box test it? Further, if your concern is an API client integrating with the API, use code generation not tests to ensure correctness! Generate your clients from a spec generated from your types! I recommend Swagger/OpenAPI or JSON Schema. Here's a nice library for doing this: https://github.com/juhaku/utoipa
-
Web frameworks with integrated Open API?
utoipa: supports most popular frameworks
-
Announcing utoipa 2.0.0, long awaited release - Compile time OpenAPI + Swagger UI
Something like that is planned in future releases. There is a closed discussion in Github https://github.com/juhaku/utoipa/issues/201 and traits for this already exists but the derive implementaiton is yet to be done.
-
okapi-operation - procedural macro for generating OpenAPI operation definitions
Those tags next function parameters look cool. Do you maybe know a crate Utoipa and could share differences between the two crates for those who want to quickly compare them? I've been using utoipa but also I've been following the discussion on Axum's repo about OpenAPI integration in hope for something more comfortable to write. Taking a quick peek they seem very similar but I'm guessing the approach is slightly different?
axum
-
Bundle frontend into axum binary using include_dir
There are some proposals on how to do it already such as https://github.com/tokio-rs/axum/issues/1698.
-
Prodzilla: From Zero to Prod with Rust and Shuttle
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: Building a secure and scalable system with Axum and SvelteKit - Part 1
CryptoFlow is a full-stack web application built with Axum and SvelteKit. It's a Q&A system tailored towards the world of cryptocurrency!
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
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.
-
My first project with rust
I build simple rust axum api server with Prisma client rust. This is my something done with rust and I really enjoyed rust!
-
Getting Started with Axum - Rust's Most Popular Framework
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.
- How serve static files with rust?
-
Trying out Leptos: Fine-grained Reactive Framework for Rust
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:
-
Help required: Port kellnr from rocket.rs to axum
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.
-
Grimoire - A recipe management application.
Web Framework : axum.
What are some alternatives?
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
swagger-core - Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
Rocket - A web framework for Rust.
socketioxide - A socket.io server implementation in Rust that integrates with the Tower ecosystem and the Tokio stack.
poem - A full-featured and easy-to-use web framework with the Rust programming language.
oaph - Helps to subtituate query params and schema definitions to openapi3/asyncapi yaml.
warp - A super-easy, composable, web server framework for warp speeds.
oatx - Generator-less JSONSchema types straight from OpenAPI spec
rust-web-framework-comparison - A comparison of some web frameworks and libs written in Rust
go - The Go programming language
rust-web-benchmarks - Benchmarking web frameworks written in rust with rewrk tool.