Analysis updated 2026-07-18 · repo last pushed 2018-04-12
Define service messages and functions once, then let gRPC-Go generate the networking code to send and receive them.
Connect a backend API to multiple microservices using a single shared communication framework.
Let a mobile app talk to a server using gRPC instead of hand-rolled HTTP request parsing.
Standardize how different teams' services communicate within a company to cut down on integration bugs.
| jyane/grpc-go | 42wim/fabio | 42wim/go-xmpp | |
|---|---|---|---|
| Language | Go | Go | Go |
| Last pushed | 2018-04-12 | 2018-02-04 | 2020-01-24 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 3/5 | 3/5 | 3/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Considered production-ready with minimal dependencies, a single install command and included examples get you started.
The official Go implementation of gRPC, a standardized framework that lets different services communicate over HTTP/2 without each team writing custom networking code.
Mainly Go. The stack also includes Go, HTTP/2, gRPC.
Dormant — no commits in 2+ years (last push 2018-04-12).
No license information was found in the explanation.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.