pasts VS tarpc

This was one of the original ideas behind pasts. I wanted to share data on a single threaded executor without using RefCell, so I created the Join struct api (renamed and redesigned many times). I'm curious what you think of that approach.

Pointing out that you're comparing apples to oranges. First off, that example isn't marked #[no_std], that means it will not work on no-std. It's not the same example. You need to define a panic handler, eh_personality and an allocator all of which are conviniently ignored in your linked example because it targets std instead of no-std. If you look at the actual equivalent example in pasts, it is actually not more boilerplate: https://github.com/ardaku/pasts/blob/stable/examples/timer.rs

You can think its better version of tarpc

tarpc is a Rust RPC crate by google (not official)

gRPC (https://github.com/google/tarpc) is the first thought here, but it is bounded to http2 and the client has to initiate the connection, I haven't used stream request before so not sure if it fits my situation.

For generating server and client code from an interface description, you may try tonic for gRPC with protobuf as your interface language, or tarpc if you want to describe the API in Rust.