Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.
Awesome Lists | Featured Topics | Projects
https://github.com/bytecodealliance/wrpc

Wasm component-native RPC framework
https://github.com/bytecodealliance/wrpc
async component-model wasm wit
Last synced: 5 days ago
JSON representation
Wasm component-native RPC framework
Host: GitHub
URL: https://github.com/bytecodealliance/wrpc
Owner: bytecodealliance
License: other
Created: 2024-01-12T20:27:36.000Z (10 months ago)
Default Branch: main
Last Pushed: 2024-11-06T13:24:33.000Z (7 days ago)
Last Synced: 2024-11-06T13:36:58.201Z (7 days ago)
Topics: async, component-model, wasm, wit
Language: Rust
Homepage:
Size: 12.1 MB
Stars: 150
Watchers: 6
Forks: 21
Open Issues: 18
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project

README

        


  wRPC


  


    

    Component-native

    transport-agnostic RPC protocol and framework based on

    WebAssembly Interface Types (WIT)

    

  


  A Bytecode Alliance hosted project

  


    

    

  



## About

wRPC facilitates execution of arbitrary functionality defined in [WIT] over network or other means of communication.

Main use cases for wRPC are:

- out-of-tree WebAssembly runtime plugins

- distributed WebAssembly component communication

Even though wRPC is designed for Wasm components first and foremost, it is fully usable outside of WebAssembly context and can serve as a general-purpose RPC framework.

wRPC uses [component model value definiton encoding] on the wire.

wRPC supports both dynamic (based on e.g. runtime WebAssembly component type introspection) and static use cases.

For static use cases, wRPC provides [WIT] binding generators for:

- Rust

- Go

wRPC fully supports the unreleased native [WIT] `stream` and `future` data types along with all currently released WIT functionality.

See [specification](./SPEC.md) for more info.

## Installation

- Using [`cargo`](https://doc.rust-lang.org/cargo/index.html):

    ```sh

    cargo install wrpc

    ```

- Using [`nix`](https://zero-to-nix.com/start/install):

    ```sh

    nix profile install github:bytecodealliance/wrpc

    ```

    or, without installing:

    ```

    nix shell github:bytecodealliance/wrpc

    ```

- You can also download individual binaries from the [release page](https://github.com/bytecodealliance/wrpc/releases)

## Quickstart

wRPC usage examples for different programming languages can be found at [examples](./examples).

There are 2 different kinds of examples:

- Native wRPC applications, tied to a particular wRPC transport (like Unix Domain Sockets, TCP, QUIC or [NATS.io])

- Generic Wasm components, that need to run in a Wasm runtime. Those can be executed, for example, using `wrpc-wasmtime`, to polyfill imports at runtime and serve exports using wRPC.

### Requirements

- For Rust components and wRPC applications: `rust` >= 1.82

- For [NATS.io] transport: `nats-server` >= 2.10.20 or [`docker`](https://www.docker.com/) >= 24.0.6 (or any other OCI runtime)

Nix users can run `nix develop` anywhere in the repository to get all dependencies correctly set up

### `hello` example

In this example we will serve and invoke a simple [`hello`](./examples/wit/hello/hello.wit) application.

#### Rust components

We will use the following two Rust components:

- [examples/rust/hello-component-client](examples/rust/hello-component-client)

- [examples/rust/hello-component-server](examples/rust/hello-component-server)

We will have to build these components first:

- Build Wasm `hello` client:

    ```sh

    cargo build --release -p hello-component-client --target wasm32-wasip2

    ```

    > Output is in target/wasm32-wasip2/release/hello-component-client.wasm

- Build Wasm `hello` server:

    ```sh

    cargo build --release -p hello-component-server --target wasm32-wasip2

    ```

    

    > Output is in target/wasm32-wasip2/release/hello_component_server.wasm

    > NB: Rust uses `_` separators in the filename, because a component is built as a reactor-style library

#### Using TCP transport

We will use the following two Rust wRPC applications using TCP transport:

- [examples/rust/hello-tcp-client](examples/rust/hello-tcp-client)

- [examples/rust/hello-tcp-server](examples/rust/hello-tcp-server)

> `[::1]:7761` is used as the default address

1. Serve Wasm `hello` server via TCP

    ```sh

    wrpc-wasmtime tcp serve ./target/wasm32-wasip2/release/hello_component_server.wasm

    ```

    - Sample output:

    > INFO wrpc_wasmtime_cli: serving instance function name="hello"

3. Call Wasm `hello` server using a Wasm `hello` client via TCP:

    ```sh

    wrpc-wasmtime tcp run ./target/wasm32-wasip2/release/hello-component-client.wasm

    ```

    - Sample output in the client:

    >hello from Rust

    - Sample output in the server:

    > INFO wrpc_wasmtime_cli: serving instance function invocation

    >

    > INFO wrpc_wasmtime_cli: successfully served instance function invocation

4. Call the Wasm `hello` server using a native wRPC `hello` client via TCP:

    ```sh

    cargo run -p hello-tcp-client

    ```

5. Serve native wRPC `hello` server via TCP:

    ```sh

    cargo run -p hello-tcp-server [::1]:7762

    ```

6. Call native wRPC `hello` server using native wRPC `hello` client via TCP:

    ```sh

    cargo run -p hello-tcp-client [::1]:7762

    ```

7. Call native wRPC `hello` server using Wasm `hello` client via TCP:

    ```sh

    wrpc-wasmtime tcp run --import [::1]:7762 ./target/wasm32-wasip2/release/hello-component-client.wasm

    ```

#### Using [NATS.io] transport

We will use the following two Rust wRPC applications using [NATS.io] transport:

- [examples/rust/hello-nats-client](examples/rust/hello-nats-client)

- [examples/rust/hello-nats-server](examples/rust/hello-nats-server)

1. Run [NATS.io] (more thorough documentation available [here](https://docs.nats.io/running-a-nats-service/introduction/running)):

    - using standalone binary:

    ```sh

    nats-server

    ```

    

    - using [Docker]:

    ```sh

    docker run --rm -it --name nats-server -p 4222:4222 nats:2.10.20-alpine3.20

    ```

2. Serve Wasm `hello` server via [NATS.io]

    ```sh

    wrpc-wasmtime nats serve --export rust ./target/wasm32-wasip2/release/hello_component_server.wasm

    ```

    

    - Sample output:

    > INFO async_nats: event: connected

    >

    > INFO wrpc_wasmtime_cli: serving instance function name="hello"

3. Call Wasm `hello` server using a Wasm `hello` client via [NATS.io]:

    ```sh

    wrpc-wasmtime nats run --import rust ./target/wasm32-wasip2/release/hello-component-client.wasm

    ```

    

    - Sample output in the client:

    > INFO async_nats: event: connected

    >

    >hello from Rust

    

    - Sample output in the server:

    > INFO wrpc_wasmtime_cli: serving instance function invocation

    >

    > INFO wrpc_wasmtime_cli: successfully served instance function invocation

4. Call the Wasm `hello` server using a native wRPC `hello` client via [NATS.io]:

    ```sh

    cargo run -p hello-nats-client rust

    ```

5. Serve native wRPC `hello` server via [NATS.io]:

    ```sh

    cargo run -p hello-nats-server native

    ```

6. Call both the native wRPC `hello` server and Wasm `hello` server using native wRPC `hello` client via [NATS.io]:

    ```sh

    cargo run -p hello-nats-client rust native

    ```

7. Call native wRPC `hello` server using Wasm `hello` client via [NATS.io]:

    ```sh

    wrpc-wasmtime nats run --import native ./target/wasm32-wasip2/release/hello-component-client.wasm

    ```

## Repository structure

This repository contains (for all supported languages):

- core libraries and abstractions

- binding generators

- WebAssembly runtime integrations

- wRPC transport implementations

`wit-bindgen-wrpc` aims to closely match UX of [`wit-bindgen`] and therefore includes a subtree merge of the project, which is occasionally merged into this tree.

- wRPC binding generators among other tests, are tested using the [`wit-bindgen`] test suite

- [`wit-bindgen`] documentation is reused where applicable

[`wit-bindgen`]: https://github.com/bytecodealliance/wit-bindgen

[component]: https://component-model.bytecodealliance.org/

[WebAssembly Interface Types (WIT)]: https://component-model.bytecodealliance.org/design/wit.html

[WIT]: https://component-model.bytecodealliance.org/design/wit.html

[component model value definiton encoding]: https://github.com/WebAssembly/component-model/blob/8ba643f3a17eced576d8d7d4b3f6c76b4e4347d7/design/mvp/Binary.md#-value-definitions

## Contributing

[![GitHub repo Good Issues for newbies](https://img.shields.io/github/bytecodealliance/issues/wrpc/good%20first%20issue?style=flat&logo=github&logoColor=green&label=Good%20First%20issues)](https://github.com/bytecodealliance/wrpc/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) [![GitHub Help Wanted issues](https://img.shields.io/github/bytecodealliance/issues/wrpc/help%20wanted?style=flat&logo=github&logoColor=b545d1&label=%22Help%20Wanted%22%20issues)](https://github.com/bytecodealliance/wrpc/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) [![GitHub Help Wanted PRs](https://img.shields.io/github/issues-pr/bytecodealliance/wrpc/help%20wanted?style=flat&logo=github&logoColor=b545d1&label=%22Help%20Wanted%22%20PRs)](https://github.com/bytecodealliance/wrpc/pulls?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) [![GitHub repo Issues](https://img.shields.io/github/bytecodealliance/issues/wrpc?style=flat&logo=github&logoColor=red&label=Issues)](https://github.com/bytecodealliance/wrpc/issues?q=is%3Aopen)

👋 **Welcome, new contributors!**

Whether you're a seasoned developer or just getting started, your contributions are valuable to us. Don't hesitate to jump in, explore the project, and make an impact. To start contributing, please check out our [Contribution Guidelines](CONTRIBUTING.md). 

[Docker]: https://www.docker.com/

[NATS.io]: https://nats.io/