drpc VS twirp

i had try drpc https://github.com/storj/drpc , it's good for my project, but , connect-go https://github.com/bufbuild/connect-go is better, for me, maybe is best one.

> But I do long for a simpler alternative

If you're happy with protobuf but just not with gRPC, you can check out Twirp [1] and DRPC [2]. Both aim to be simpler alternatives while keeping protobuf for serialization. Their development is Go focused though.

[1] https://github.com/twitchtv/twirp

[2] https://github.com/storj/drpc/

Someone opened an issue talking about adding websocket support. Since it seems fairly easy to add, I'll probably write an external package to do it so that DRPC's dependencies don't grow.

The next time I want to build an API, I will probably make use of https://github.com/twitchtv/twirp. I like working with Protobuf and having strongly-typed and well-defined messages, but gRPC is way, way too much. It's obviously a Google product, built for what Google needs.

Use Protobuf for messages, but just use HTTP for transport.

- Twirp (Twitch light version of gRPC, with optional JSON encoding, HTTP1 support and without streaming) - https://github.com/twitchtv/twirp

There is another: twirp

And addition to what was mentioned there are also webrpc and twirp.

If you find one, you maybe also interested in twirp.

Twitch has a great framework for it https://twitchtv.github.io/twirp/docs/intro.html

We have better experience with https://goa.design/ than with https://github.com/twitchtv/twirp

Take a look at Twirp (https://github.com/twitchtv/twirp) open sourced by TwitchTv. It's a lot lighter weight than gRPC. It does use Protobufs but addresses some of the concerns you mentioned, such as being able to test with JSON payloads, works over HTTP 1.1 and HTTP/2, good client libraries, and doesn't require a proxy.

They address your concerns in more detail in the Twirp release announcement (2018) - https://blog.twitch.tv/en/2018/01/16/twirp-a-sweet-new-rpc-f...