Async::GRPC

Asynchronous gRPC client and server implementation built on top of protocol-grpc and async-http.

Features

async-grpc provides asynchronous networking and concurrency for gRPC:

Asynchronous client - Wraps Async::HTTP::Client to provide gRPC-specific call methods with automatic message framing and status handling.
Method-based stubs - Create type-safe stubs from Protocol::GRPC::Interface definitions. Accepts both PascalCase and snake_case method names for convenience.
Server middleware - Dispatcher routes requests to registered services based on path.
All RPC patterns - Supports unary, server streaming, client streaming, and bidirectional streaming RPCs.
HTTP/1 and HTTP/2 transport - Built on async-http with automatic HTTP/2 multiplexing and connection pooling.

Usage

Please browse the source code index or refer to the guides below.

Getting Started

This guide explains how to get started with Async::GRPC for building gRPC clients and servers.

Releases

Please browse the releases for more details.

Unreleased

Breaking: Renamed DispatcherMiddleware to Dispatcher for cleaner API.
Breaking: Simplified Dispatcher#register API to register(service, name: service.service_name), eliminating redundant service name specification.

v0.2.0

Added Async::GRPC::RemoteError class to encapsulate remote error details including message and backtrace extracted from response headers.
Client-side error handling now extracts backtraces from response metadata and sets them on RemoteError, which is chained as the cause of Protocol::GRPC::Error for better debugging.
Updated to use Protocol::GRPC::Metadata.add_status! instead of deprecated add_status_trailer! method.
Tidy up request and response body handling.

v0.1.0

Initial hack.

Contributing

We welcome contributions to this project.

Fork it.
Create your feature branch (git checkout -b my-new-feature).
Commit your changes (git commit -am 'Add some feature').
Push to the branch (git push origin my-new-feature).
Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.