tiny-http
Rouille, Rust web server middleware
Our great sponsors
tiny-http | Rouille, Rust web server middleware | |
---|---|---|
5 | 15 | |
951 | 1,067 | |
1.6% | - | |
1.5 | 1.0 | |
17 days ago | 19 days 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.
tiny-http
-
C-rusted: The Advantages of Rust, in C, without the Disadvantages
kcgi describes itself as being "minimal" whereas actix-web calls itself "powerful", "extremely fast" and as having "a lot of features out of box"... seems about as fair as comparing the 320MB Apache HTTP Server repo against the 52KB tiny_http library
-
Is Rust good choice for the backend of any mobile application?
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 .
-
Hey rustaceans, which web framework you guys suggest for a small application?
tiny-http is small. You'll probably be able to make something with less than 1 Mb.
-
NVD - CVE-2022-23812 - A 9.8 critical vulnerability caused by a node library author adding code into his package which has a 1 in 4 chance of wiping the files of a system if it's IP comes from Russia or Belarus
That's not a simple http server, something like tiny_http would be with only... 17 total dependencies by default. Actix is a full framework with an abundance of features, and correspondingly-large dependency tree.
- GitHub - tiny-http/tiny-http: Low level HTTP server library in 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?
rustful - [OUTDATED] A light HTTP framework for Rust
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
url-crawler - Rust crate for configurable parallel web crawling, designed to crawl for content
Rocket - A web framework for Rust.
The FastCGI Rust implementation. - Native Rust library for FastCGI
Nickel - An expressjs inspired web framework for Rust
Rustless - REST-like API micro-framework for Rust. Works with Iron.
handlebars-iron - Handlebars middleware for Iron web framework
moonfire-nvr - Moonfire NVR, a security camera network video recorder