trillium
Rouille, Rust web server middleware
trillium | Rouille, Rust web server middleware | |
---|---|---|
6 | 15 | |
318 | 1,076 | |
2.5% | - | |
9.6 | 1.0 | |
5 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.
trillium
-
Hey rustaceans, which web framework you guys suggest for a small application?
i like trillium a lot. inspired by plug (elixir), you just add plugs in a vertical stack and the request goes from top to bottom. there is also ntex which has a ton of examples inspired by actix-web (might have been a fork) https://github.com/ntex-rs/examples
-
A struct field that's either a Reference or Value
Maybe you want something like this, which is a Cow-like enum that either holds a &mut T or a T?
-
New Tokio blog post: Announcing Axum - Web framework that focuses on ergonomics and modularity
I've been planning on using trillium on a project, the main difference I can see between it and Axum is that Axum allows you to use existing tower middle ware, right?
-
Trillium web framework
I'll definitely prioritize this! I hadn't really thought much about it because it's straightforward to do in application code, but it seems reasonable to make it easier for people to get started with this common use case. I opened up a discussion on gh, let me know if something like what you had in mind https://github.com/trillium-rs/trillium/discussions/36
-
New Tower guide: Building a middleware from scratch
Any thoughts on (trillium)[https://github.com/trillium-rs/trillium]? Looks like you're fulfilling similar niches.
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.
rust-web-framework-comparison - A comparison of some web frameworks and libs written in Rust
tiny-http - Low level HTTP server library in Rust
tower-http - HTTP specific Tower utilities.
Rocket - A web framework for Rust.
jelly-actix-web-starter - A starter template for actix-web projects that feels very Django-esque. Avoid the boring stuff and move faster.
Nickel - An expressjs inspired web framework for Rust
dropshot - expose REST APIs from a Rust program
Rustless - REST-like API micro-framework for Rust. Works with Iron.
tonic - A native gRPC client & server implementation with async/await support.
handlebars-iron - Handlebars middleware for Iron web framework