ics-proxy
sozu
| ics-proxy | sozu | |
|---|---|---|
| 5 | 8 | |
| 8 | 2,839 | |
| - | 1.2% | |
| 4.5 | 9.4 | |
| 13 days ago | 6 days ago | |
| Rust | Rust | |
| GNU General Public License v3.0 only | GNU Affero General Public License v3.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.
ics-proxy
-
Announcing Actix Web v4.0
Just updated my small web application (ics proxy).
-
I created a self-hosted open source ics-proxy in Rust
Oh yeah sorry, maybe should have linked to GitHub directly.
- I created an ics-proxy server for my university schedule
-
How to improve my code and avoid nesting of match statements?
I am fairly new to rust and created a web app with it, however, I think my code could use some improvement and I would like to get some tips and suggestions.
-
Help me improve my code! I created an ics-proxy in rust with actix.
The code is available at: https://github.com/13hannes11/ics-proxy
sozu
-
Erlang: More Optimizations in the Compiler and JIT
This is interesting, thank you.
I really should learn from BEAM and the OTP and learn Erlang. I get the feeling it's super robust and reliable and low maintenance. I wrote a userspace multithreaded scheduler which distributes N lightweight threads to M kernel threads.
https://github.com/samsquire/preemptible-thread
I recently wrote a JIT compiler and got lazy compilation of machine code working and I'm nowhere near beginning optimisation
https://github.com/samsquire/compiler
How do you write robust software, that doesn't crash when something unexpected goes on?
I looked at sozo https://github.com/sozu-proxy/sozu
and I'm thinking how to create something that just stays up and running regardless.
-
Open Source HTTP Reverse Proxy Built in Rust for Immutable Infrastructures
It's AGPL licensed which for a proxy is a strange choice. They have an unanswered question for months on what it might mean: https://github.com/sozu-proxy/sozu/issues/764
Without an answer to that if you use this and you need to make any change to it (even a tiny bug fix), you're basically opening yourself up a pile of legal issues.
-
Rust-based reverse proxy?
Sozu: Well documented, runtime configurable proxy
-
Do most people just restart their Rust web servers once every three months?
https://github.com/sozu-proxy/sozu https://github.com/sozu-proxy/sozu/blob/main/doc/design_motivation.md
-
Force all rust application traffic to pass from proxy.
Could sozu or rathole or leaf or exodus somehow help?
-
Scalable server design in Rust with Tokio
it is not sufficient: a listen socket has its own queue of new TCP connections (that were already handshaked by the kernel), so dropping the listen socket drops the queue. The right way is to start the new server, transfer the listen socket from the old server to the new one with SCM_RIGHTS, then start accepting again from the new instance. That's how it is done in the sozu HTTP proxy (which also uses SO_REUSEPORT to launch multiple work processes each with their own listeners, to improve performance and isolate failure)
-
Any thoughts about Clever Cloud? (Has native rust support.)
BTW that traffic will be coming from our sozu load balancers, built in Rust too ;)
-
ARLB: A very experimental load balancer/reverse proxy based on hyper and tokio
How does it compare to sozu?
What are some alternatives?
eskom-calendar - Get your loadshedding schedule in your calendar and never be left in the dark! Open-source, up-to-date, and developer friendly.
another-rust-load-balancer - A load balancer with support for different middlewares and load balancing strategies, based on hyper and tokio