tonic
tokio
Our great sponsors
tonic | tokio | |
---|---|---|
48 | 196 | |
8,966 | 24,677 | |
3.5% | 2.8% | |
8.6 | 9.5 | |
about 20 hours ago | 1 day ago | |
Rust | Rust | |
MIT License | MIT 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.
tonic
-
Roll your own auth with Rust and Protobuf
Use tonic-build directly from Rust.
-
How to limit different concurrency number by service on Tonic?
} // Omit the remaining code and refer to the example in Tonic: https://github.com/hyperium/tonic/blob/master/examples/src/multiplex/server.rs ```
-
Ideas/Suggestions around setting up a data pipeline from scratch
If I’m not misunderstanding, you could both decode the gRPC protobuf AND write to delta lake in Rust. Tonic, Delta-rs.
-
Throughput doesn't increase with cores/threads count
Original post: https://github.com/hyperium/tonic/issues/1405. Cross-post here in case the problem is not specific to tonic.
-
Getting started with gRPC in Rust
Tonic
-
libp2p alternate
Just to double check Is this the correct repo?
-
Spaceman: A gRPC client from another world. Comes both as a CLI and as a GUI built with Tauri and Yew.rs
Wasm isn't involved much actually. Basically, the frontend asks the backend to perform a gRPC call on its behalf using Tauri events. They are like named channels on which you can send any serde-compatible value. But the backend is a normal Rust program so there are no constraints there. I use prost-reflect to encode/decode Protobuf messages according to Protobuf descriptors loaded at runtime and make the actual requests using tonic from the tokio ecosystem. prost-reflect is necessary because, normally, tonic expects the Protobuf descriptor to be known at compile time so it can make some code generation behind the scenes.
-
Is there something like Feathersjs for Rust?
You could have a look at gRPC i.e. https://github.com/hyperium/tonic
-
Tower - middleware or interceptor
Looking at this example code: https://github.com/hyperium/tonic/blob/master/examples/src/tower/server.rs
-
Keyword Generics Progress Report: February 2023 | Inside Rust Blog
The remaining gap is remote actors, since you still need some kind of serialization between them, and take your pick of standards for that one such as gRPC using Tonic.
tokio
-
On Implementation of Distributed Protocols
Being able to control nondeterminism is particularly useful for testing and debugging. This allows creating reproducible test environments, as well as discrete-event simulation for faster-than-real-time simulation of time delays. For example, Cardano uses a simulation environment for the IO monad that closely follows core Haskell packages; Sui has a simulator based on madsim that provides an API-compatible replacement for the Tokio runtime and intercepts various POSIX API calls in order to enforce determinism. Both allow running the same code in production as in the simulator for testing.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
tokio - An asynchronous runtime for Rust
-
Top 10 Rusty Repositories for you to start your Open Source Journey
3. Tokio
-
API Gateway, Lambda, DynamoDB and Rust
The AWS SDK makes use of the async capabilities in the Tokio library. So when you see async in front of a fn that function is capable of executing asynchronously.
-
The More You Gno: Gno.land Monthly Updates - 6
Petar is also looking at implementing concurrency the way it is in Go to have a fully functional virtual machine as it is in the spec. This would likely attract more external contributors to developing the VM. One advantage of Rust is that, with the concurrency model, there is already an extensive library called Tokio which he can use. Petar stresses that this isn’t easy, but he believes it’s achievable, at least as a research topic around determinism and concurrency.
-
Consuming an SQS Event with Lambda and Rust
Another thing to point out is that async is a thing in Rust. I'm not going to begin to dive into this paradigm in this article, but know it's handled by the awesome Tokio framework.
-
netcrab: a networking tool
So I started by using Tokio, a popular async runtime. The docs and samples helped me get a simple outbound TCP connection working. The Rust async book also had a lot of good explanations, both practical and digging into the details of what a runtime does.
-
Thread-per-Core
Regarding the quote:
> The Original Sin of Rust async programming is making it multi-threaded by default. If premature optimization is the root of all evil, this is the mother of all premature optimizations, and it curses all your code with the unholy Send + 'static, or worse yet Send + Sync + 'static, which just kills all the joy of actually writing Rust.
Agree about the melodramatic tone. I also don't think removing the Send + Sync really makes that big a difference. It's the 'static that bothers me the most. I want scoped concurrency. Something like <https://github.com/tokio-rs/tokio/issues/2596>.
Another thing I really hate about Rust async right now is the poor instrumentation. I'm having a production problem at work right now in which some tasks just get stuck. I wish I could do the equivalent of `gdb; thread apply all bt`. Looking forward to <https://github.com/tokio-rs/tokio/issues/5638> landing at least. It exists right now but is experimental and in my experience sometimes panics. I'm actually writing a PR today to at least use the experimental version on SIGTERM to see what's going on, on the theory that if it crashes oh well, we're shutting down anyway.
Neither of these complaints would be addressed by taking away work stealing. In fact, I could keep doing down my list, and taking away work stealing wouldn't really help with much of anything.
-
PHP-Tokio – Use any async Rust library from PHP
The PHP <-> Rust bindings are provided by https://github.com/Nicelocal/ext-php-rs/ (our fork of https://github.com/davidcole1340/ext-php-rs with a bunch of UX improvements :).
php-tokio's integrates the https://revolt.run event loop with the https://tokio.rs event loop; async functionality is provided by the two event loops, in combination with PHP fibers through revolt's suspension API (I could've directly used the PHP Fiber API to provide coroutine suspension, but it was a tad easier with revolt's suspension API (https://revolt.run/fibers), since it also handles the base case of suspension in the main fiber).
What are some alternatives?
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
async-std - Async version of the Rust standard library
grpc-rust - Rust implementation of gRPC
Rocket - A web framework for Rust.
tarpc - An RPC framework for Rust with a focus on ease of use.
hyper - An HTTP library for Rust
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
futures-rs - Zero-cost asynchronous programming in Rust
prost - PROST! a Protocol Buffers implementation for the Rust Language
smol - A small and fast async runtime for Rust
rust-prometheus - Prometheus instrumentation library for Rust applications
rayon - Rayon: A data parallelism library for Rust