loco
Rouille, Rust web server middleware
loco | Rouille, Rust web server middleware | |
---|---|---|
9 | 15 | |
3,404 | 1,078 | |
11.8% | - | |
9.8 | 1.0 | |
3 days ago | about 1 month ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
loco
-
PHP in 2024
Well, no, that's not really a fair assessment. Someone is quite literally doing "rails but for Rust" with loco: https://loco.rs
As far as I know, the bulk of this effort has been one developer pushing it along. I wouldn't personally use it but it _does_ exist.
It's also worth noting that these older frameworks all come from a different era of development - nowadays most newer devs seem to want to build microservice-after-microservice, where these don't quite fit into the picture.
-
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.
-
Introducing Loco: The Rails of Rust
Interested in more? Check out the full tour of Loco here. Check out their discussions here.
-
New Rust Framework: With JavaScript Server-Side Rendering for the UI
Try https://loco.rs/ or maybe tell us what to add?
- Loco: The one-person Rust framework for side-projects and startups
- Loco: the one-person framework for Rust for side-projects and startups
- Loco. The one-person framework for Rust for side-projects and startups
- Loco-rs: releasing a framework inspired by Rails on Rust
Rouille, Rust web server middleware
- Rouille, a Rust web micro-framework
-
Async rust – are we doing it all wrong?
Your CRUD web application server almost certainly doesn't need async Rust. Using a blocking HTTP server is not "might be a good idea", it simply is a good idea.
I recommend Rouille for this: https://github.com/tomaka/rouille. In case you are worried about performance, check the benchmark. Blocking Rouille is faster than builtin async server in Node.js.
-
Best backend web frameworks with blocking io (i.e. not async)?
As you say, the majority of the web ecosystem in Rust has moved to async - but if you’re happy to stray a bit from the beaten path then rouille might do the trick.
-
An Express-inspired web framework for Rust
In strongly typed languages like Rust, composing smaller libraries is usually quite painless, so you don't need a large framework.
Personally for backend Rust I use rouille[0] for the server (it's very simple and async-free), askama[1] for compile-time HTML templates and (if a SPA is unavoidable, as that is of course always to be avoided if at all possible) yew[2] for client-side WASM.
Now this stack is what I like personally, but there are many options that you can combine, some more full-featured than others. Check out https://www.arewewebyet.org/ for a partial overview.
[0]: https://github.com/tomaka/rouille
[1]: https://github.com/djc/askama
[2]: https://yew.rs/
-
Which Rust web framework to choose in 2022 (with code examples)
rouille
I'd like to put in a word for a simple, sync framework such as rouille. The compile times are much, much better, the number of dependencies is much smaller, the stuff it's built on (the standard library) is extensively tested and extremely reliable. Kernel context switches are slower than userspace thread scheduling, but not much slower, and as long as your services aren't just shoving bytes from one place to another (i.e. actually doing some computation) the time taken for a context switch vanishes into noise. A lot of benchmarks test how quickly a web service can move bytes, which (if your business logic is non-trivial) actually isn't the most critical factor.
-
Hey rustaceans, which web framework you guys suggest for a small application?
I don't have any Rust-relevant experience here, but if I wanted to build a web server in Rust and was okay with "reasonable" performance, I'd probably give rouille a try first.
-
The Rustacean way to build a complete web app?
Rouille is fairly solid in my experience. Save the pain of async and spend it building software that works. Honestly with Rust's lack of GC you get predictable response times already.
- Des avis sur mon cadeau?
-
vial: a really tiny web framework
How would you differentiate it from let's say Rouille ?
What are some alternatives?
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
Rocket - A web framework for Rust.
tiny-http - Low level HTTP server library in Rust
Ackpine - Android package installer library
The FastCGI Rust implementation. - Native Rust library for FastCGI
Nickel - An expressjs inspired web framework for Rust
kubernetes-rust - Rust client for Kubernetes
Rustless - REST-like API micro-framework for Rust. Works with Iron.
eww - ElKowars wacky widgets
handlebars-iron - Handlebars middleware for Iron web framework