grpc-elixir alternatives and similar packages
Based on the "Protocols" category.
Alternatively, view grpc-elixir alternatives based on common mentions on social networks and blogs.
-
msgpax
High-performance and comprehensive MessagePack implementation for Elixir / msgpack.org[Elixir] -
protox
A fast, easy to use and 100% conformant Elixir library for Google Protocol Buffers (aka protobuf)
CodeRabbit: AI Code Reviews for Developers

Do you think we are missing an alternative of grpc-elixir or a related project?
README
gRPC Elixir
An Elixir implementation of gRPC.
WARNING: Be careful to use it in production! Test and benchmark in advance.
NOTICE: Erlang/OTP needs >= 20.3.2
NOTICE: grpc_gun
Now {:gun, "~> 2.0.0", hex: :grpc_gun}
is used in mix.exs because grpc depnds on Gun 2.0,
but its stable version is not released. So I published a 2.0 version on hex
with a different name. So if you have other dependencies who depends on Gun, you need to use
override: {:gun, "~> 2.0.0", hex: :grpc_gun, override: true}
. Let's wait for this issue
https://github.com/ninenines/gun/issues/229.
Installation
The package can be installed as:
def deps do
[
{:grpc, github: "elixir-grpc/grpc"},
# 2.9.0 fixes some important bugs, so it's better to use ~> 2.9.0
{:cowlib, "~> 2.9.0", override: true}
]
end
Usage
- Generate Elixir code from proto file as protobuf-elixir shows(especially the
gRPC Support
section). - Implement the server side code like below and remember to return the expected message types. ```elixir defmodule Helloworld.Greeter.Server do use GRPC.Server, service: Helloworld.Greeter.Service
@spec say_hello(Helloworld.HelloRequest.t, GRPC.Server.Stream.t) :: Helloworld.HelloReply.t def say_hello(request, _stream) do Helloworld.HelloReply.new(message: "Hello #{request.name}") end end
3. Start the server
You can start the gRPC server as a supervised process. First, add `GRPC.Server.Supervisor` to your supervision tree.
```elixir
# Define your endpoint
defmodule Helloworld.Endpoint do
use GRPC.Endpoint
intercept GRPC.Logger.Server
run Helloworld.Greeter.Server
end
# In the start function of your Application
defmodule HelloworldApp do
use Application
def start(_type, _args) do
children = [
# ...
supervisor(GRPC.Server.Supervisor, [{Helloworld.Endpoint, 50051}])
]
opts = [strategy: :one_for_one, name: YourApp]
Supervisor.start_link(children, opts)
end
end
Then start it when starting your application:
# config.exs
config :grpc, start_server: true
# test.exs
config :grpc, start_server: false
$ iex -S mix
or run grpc.server using a mix task
$ mix grpc.server
- Call rpc: ```elixir iex> {:ok, channel} = GRPC.Stub.connect("localhost:50051") iex> request = Helloworld.HelloRequest.new(name: "grpc-elixir") iex> {:ok, reply} = channel |> Helloworld.Greeter.Stub.say_hello(request)
With interceptors
iex> {:ok, channel} = GRPC.Stub.connect("localhost:50051", interceptors: [GRPC.Logger.Client]) ...
Check [examples](examples) and [interop](interop)(Interoperability Test) for some examples.
## TODO
- [x] Unary RPC
- [x] Server streaming RPC
- [x] Client streaming RPC
- [x] Bidirectional streaming RPC
- [x] Helloworld and RouteGuide examples
- [x] Doc and more tests
- [x] Authentication with TLS
- [x] Improve code generation from protos ([protobuf-elixir](https://github.com/tony612/protobuf-elixir) [#8](https://github.com/elixir-grpc/grpc/issues/8))
- [x] Timeout for unary calls
- [x] Errors handling
- [x] Benchmarking
- [x] Logging
- [x] Interceptors(See `GRPC.Endpoint`)
- [x] [Connection Backoff](https://github.com/grpc/grpc/blob/master/doc/connection-backoff.md)
- [x] Data compression
- [x] Support other encoding(other than protobuf)
## Benchmark
1. [Simple benchmark](examples/helloworld/README.md#Benchmark) by using [ghz](https://ghz.sh/)
2. [Benchmark](benchmark) followed by official spec
## Sponsors
This project is being sponsored by [Tubi](https://tubitv.com/). Thank you!
<img src="https://user-images.githubusercontent.com/1253659/37473536-4db44048-28a9-11e8-90d5-f8a2f5a8d53c.jpg" height="80">
## Contributing
You contributions are welcome!
Please open issues if you have questions, problems and ideas. You can create pull
requests directly if you want to fix little bugs, add small features and so on.
But you'd better use issues first if you want to add a big feature or change a
lot of code.