zenoh
quiche
zenoh | quiche | |
---|---|---|
13 | 26 | |
1,259 | 8,953 | |
3.9% | 1.6% | |
9.6 | 9.0 | |
5 days ago | about 22 hours ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | BSD 2-clause "Simplified" 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.
zenoh
- Zenoh: Zero Overhead Network Protocol
- Eclipse Zenoh 0.10.0 is out
-
Can I use several async runtimes in the same project?
I'm very new to Rust and currently I'm trying to make sense of async programming in Rust. In my project I'm trying to create an http + websocket server (I picked Actix) that communicates to a CPP program over DDS and sends the result of this communication to some frontend over http/ws. I use Zenoh for leveraging communication between my Rust app and CPP, and it has it's own crate for creating a zenoh client in Rust. In the documentation they use async-std macros for the main function and Actix uses Tokio under the hood, as far as I understand. Is this gonna be a problem? Can I have several async runtimes in my project?
- Need recommendations for technologies, frameworks etc. for an IoT device project in Rust
-
Anouncing `stabby` 1.0!
Zenoh's plugin system was one of the main motivators for building stabby. However, Zenoh needs me on other fronts at the moment, so stabby will have to go to the back burner for a bit. This doesn't mean stabby will become unsupported: if you want to use it, and are having a hard time, feel free to DM me to get some support. In fact, what stabby needs most right now is feedback on what types you'd like to see supported, so go for it!
- Zenoh – Zero Overhead Network Protocol
-
Zenoh Performances
Hello u/ComeGateMeBro, in zenoh we have zero-copy support, this is an example that shows how to use it: https://github.com/eclipse-zenoh/zenoh/blob/master/examples/examples/z_pub_shm.rs
-
Rust MPI -- Will there ever be a fully oxidized implementation?
The next step would be to use the zenoh crate, which will simplify a lot of things.
-
This week in Rust 479 - Eclipse Zenoh release
The new Eclipse Zenoh 0.7.0 release, codename Charmander, brings to the table many features requested by the community on the Zenoh’s Discord server.
-
Eclipse Zenoh: 0.7.0 release
The Rust code is hosted here: https://github.com/eclipse-zenoh/zenoh While the Rust docs is hosted here: https://docs.rs/zenoh/0.7.0-rc/zenoh/ It's available on crates.io: https://crates.io/crates/zenoh
quiche
-
Nghttp3 1.0.0 – HTTP/3 library written in C
The title of this post puts emphasis on "written in C", making me wonder when this would ever be a desirable feature, given that more secure implementations are available, and can be integrated into old C projects just as easily.
No need to rewrite everything from the ground up: https://github.com/cloudflare/quiche#curl
-
Curl HTTP/3 with quiche discouraged
The issue is dead silent too!
https://github.com/cloudflare/quiche/issues/1115
- Best performing quic implementation?
-
Oxy is Cloudflare's Rust-based next generation proxy framework
Even though Oxy is a proprietary project, we try to give back some love to the open-source community without which the project wouldn’t be possible by open-sourcing some of the building blocks such as https://github.com/cloudflare/boring and https://github.com/cloudflare/quiche.
-
How Rust and Wasm power Cloudflare's 1.1.1.1
They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun
-
What is a CDN? How do CDNs work?
It's more like Cloudflare forked nginx a long time ago, and is meanwhile in the very slow (like, decade-long) process of replacing it entirely.
The Cloudflare Workers Runtime, for instance, is built directly around V8; it does not use nginx or any other existing web server stack. Many new features of Cloudflare are in turn built on Workers, and much of the old stack build on nginx is gradually being migrated to Workers. https://workers.dev https://github.com/cloudflare/workerd
In another part of the stack, there is Pingora, another built-from-scratch web server focused on high-performance proxying and caching: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...
Even when using nginx, Cloudflare has rewritten or added big chunks of code, such as implementing HTTP/3: https://github.com/cloudflare/quiche And of course there is a ton of business logic written in Lua on top of that nginx base.
Though arguably, Cloudflare's biggest piece of magic is the layer 3 network. It's so magical that people don't even think about it, it just works. Seamlessly balancing traffic across hundreds of locations without even varying IP addresses is, well, not easy.
I could go on... automatic SSL provisioning? DDoS protection? etc. These aren't nginx features.
So while Cloudflare may have gotten started being more-or-less nginx-as-a-service I don't think you can really call it that anymore.
(I'm the tech lead for Cloudflare Workers.)
- Using WebTransport
-
Is it better to learn web development with Python or C?
Ask Cloudflare why they use HTTP/3 and QUIC https://github.com/cloudflare/quiche.
- DNS-over-HTTP/3 in Android
-
The MQTT broker powering Cloudflare's new Pub/Sub product is written in Rust!
Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.
What are some alternatives?
zmq.rs - A native implementation of ØMQ in Rust
quinn - Async-friendly QUIC implementation in Rust
areg-sdk - AREG is an asynchronous Object RPC framework to simplify multitasking programming by blurring borders between processes and treating remote objects as if they coexist in the same thread.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
sniffnet - Comfortably monitor your Internet traffic 🕵️♂️
quic-go - A QUIC implementation in pure Go
libpnet - Cross-platform, low level networking using the Rust programming language.
shadowsocks-rust - A Rust port of shadowsocks
MIO - Metal I/O library for Rust.
neqo - Neqo, an implementation of QUIC in Rust
canary - Distributed systems library for making communications through the network easier, while keeping minimalism and flexibility.
s2n-quic - An implementation of the IETF QUIC protocol