[RPC] Introduce a rust RPC framework

[jolestar]

We need to choose a rust RPC framework and consider the following requirements.

1. It can run a standalone server.
2. It can easily be embedded into another system(MoveOS also is a library).
3. Javascript SDK friendly, REST or JSON-RPC?

Dependency

11

[lshoo]

In rust language, RPC has more star in github are jsonrpc and jsonrpsee, and jsonrpsee is the successor of the former, and they are both produced by ParityTech：

jsonrpsee Features

• Client/server HTTP/HTTP2 support
• Client/server WebSocket support
• Client WASM support via web-sys
• Client transport abstraction to provide custom transports
• Middleware
• Logger

[pause125]

jsonrpsee is so new, is it stable enough?

[lshoo]

jsonrpsee is so new, is it stable enough?

jsonrpsee used in Subsbtrate, Sui. Or what better options are available

[pause125]

jsonrpsee is so new, is it stable enough?

jsonrpsee used in Subsbtrate, Sui. Or what better options are available

If jsonsee is stable enough, it's offcause a good choice. I 'm not familiar with RPC Frameworks.

[lshoo]

Add another option: tarpc, 25k stars in github, the Distributed tracing feature is useful: tarpc differentiates itself from other RPC frameworks by defining the schema in code, rather than in a separate language such as .proto. This means there's no separate compilation process, and no context switching between different languages.

Some other features of tarpc:

• Pluggable transport: any type implementing Stream<Item = Request> + Sink<Response> can be used as a transport to connect the client and server.
• Send + 'static optional: if the transport doesn't require it, neither does tarpc!
• Cascading cancellation: dropping a request will send a cancellation message to the server. The server will cease any unfinished work on the request, subsequently cancelling any of its own requests, repeating for the entire chain of transitive dependencies.
• Configurable deadlines and deadline propagation: request deadlines default to 10s if unspecified. The server will automatically cease work when the deadline has passed. Any requests sent by the server that use the request context will propagate the request deadline. For example, if a server is handling a request with a 10s deadline, does 2s of work, then sends a request to another server, that server will see an 8s deadline.
• Distributed tracing: tarpc is instrumented with tracing primitives extended with OpenTelemetry traces. Using a compatible tracing subscriber like Jaeger, each RPC can be traced through the client, server, and other dependencies downstream of the server. Even for applications not connected to a distributed tracing collector, the instrumentation can also be ingested by regular loggers like env_logger.
• Serde serialization: enabling the serde1 Cargo feature will make service requests and responses Serialize + Deserialize. It's entirely optional, though: in-memory transports can be used, as well, so the price of serialization doesn't have to be paid when it's not needed.

[jolestar]

11 #49 #60 finished