simple_gopher
Boilerplate for writing Go applications without framework using hexagonal application development approach (by doppelganger113)
twirp
A simple RPC framework with protobuf service definitions (by twitchtv)
simple_gopher | twirp | |
---|---|---|
3 | 30 | |
33 | 6,828 | |
- | 0.5% | |
1.2 | 3.5 | |
about 1 year ago | about 1 month ago | |
Go | Go | |
- | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
simple_gopher
Posts with mentions or reviews of simple_gopher.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-14.
twirp
Posts with mentions or reviews of twirp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-26.
-
I Reviewed 1,000s of Opinions on gRPC
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.
- How do I provide bot RPC and REST endpoints?
- Reasons to use gRPC/Protobuf?
-
A detailed comparison of REST and gRPC
- Twirp (Twitch light version of gRPC, with optional JSON encoding, HTTP1 support and without streaming) - https://github.com/twitchtv/twirp
-
goRPC or gRPC?
There is another: twirp
-
TypeScript type safety with GO
And addition to what was mentioned there are also webrpc and twirp.
-
Any good open source python projects that have used GRPC?
If you find one, you maybe also interested in twirp.
-
GraphQL making its way into a Twitter discussion about latency is not what I expected
Twitch has a great framework for it https://twitchtv.github.io/twirp/docs/intro.html
-
swaggo/swag alternative, but should generate OpenAPI 3.0 spec file
We have better experience with https://goa.design/ than with https://github.com/twitchtv/twirp
-
Connect-Web: It's time for Protobuf/gRPC to be your first choice in the browser
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...