grpc-microservice-example
gogoprotobuf
grpc-microservice-example | gogoprotobuf | |
---|---|---|
3 | 8 | |
90 | 5,632 | |
- | 0.1% | |
8.5 | 0.0 | |
3 days ago | 9 months ago | |
Go | Go | |
MIT License | GNU General Public License v3.0 or later |
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.
grpc-microservice-example
-
gRPC: Where to put the output files after compiling with protoc
Anyways, my recommendation would be to keep the generated files out of where the proto files live, to clearly separate them, I have an example of that here.
-
I wrote a tool to check available updates in go.mod
If you want something automated to open PRs, Github provides dependabot for something similar, example
-
Vending and Generating Protobuf Repo to multiple clients
Here's a working example of how to use buf; the part where other repos import the generated is something I will cover in future videos.
gogoprotobuf
-
Why Does gRPC Insist on Trailers?
That probably won't happen either, because the Google gRPC team is also quite resistant to any kind of change (that isn't driven by internal needs at Google). Projects like GoGo Protobuf had to be developed to fill gaps that the Google team refused to fill or accept PRs for.
-
Anyone needs a (long-term) contributor for their open source project written in Go?
the gogo protobuf compiler toolchain is looking for a maintainer https://github.com/gogo/protobuf u/MehdiHK
-
Distributed IM Service in Golang
protobuff : Google's binary data transfer protocol
-
Crowdstrike releases replacement for Gogo/protobuf
Looks like Crowdstrike just pushed out publicly a replacement for gogo/proto. It looks like the library solves 2 problems:
-
2022-01-11 gRPC benchmark results
Seems like we're pretty middle of the road. I can only guess as to why but it probably has to do with heavy usage of pointers and reflection. Gogo/protobuf solved this performance with code generation, but the go protobuf implementation has essentially eschewed it. I do wonder how the benchmark would look using the new vitess proto library for Go (which has many of the benefits of gogo but with active development and an API built on top of the Google one)
-
Go-generated protobufs with map[string]interface{}
Yeah, it's a pretty thick Makefile and set of shell scripts, but it's seemingly using things like: k8s.io/code-generator/cmd/go-to-protobuf and github.com/gogo/protobuf/protoc-gen-gogo and github.com/gogo/protobuf/protoc-gen-gogofast which from what I can tell... [it looks like this can probably help me a bit in understanding how to make custom types](https://cloud.redhat.com/blog/kubernetes-deep-dive-code-generation-customresources).
-
🐱👓 PowerProto: One-click installation and version control of gRPC toolchain (protoc, protoc-gen-go)
repositories: # Definition depends on the 27156597fdf4fb77004434d4409154a230dc9a32 version of https://github.com/googleapis/googleapis # and defines its name as GOOGLE_APIS # It can be referenced in importPaths by $GOOGLE_APIS GOOGLE_APIS: https://github.com/googleapis/googleapis@27156597fdf4fb77004434d4409154a230dc9a32 # Definition depends on the 226206f39bd7276e88ec684ea0028c18ec2c91ae version of https://github.com/gogo/protobuf # and defines its name as GOGO_PROTOBUF # It can be referenced in the importPaths by $GOGO_PROTOBUF GOGO_PROTOBUF: https://github.com/gogo/protobuf@226206f39bd7276e88ec684ea0028c18ec2c91ae
-
Обережно кодогенерація
В проекті ми використовуємо офіційну бібліотеку Protobuf github.com/protocolbuffers/protobuf, яка підчас серіалізації використовує рефлексію і будує слайс байтів через append. А потім я дізнався про "Protocol Buffers for Go with Gadgets" github.com/gogo/protobuf, бібліотеку-fork яка генерує додатковий код щоб прибрати рефексію підчас серіалізації і вже записує в слайс байтів по індексу бо так швидше. Коли змінював одну бібліотеку на іншу то важливим вважав що стало працювати швидше і написані раніше тести пройшли успішно. І все б було гаразд але в проекті існувала латка яка через пару тижнів після заміни перезапустила мікросервіс через паніку:
What are some alternatives?
buf - The best way of working with Protocol Buffers.
asn1
casbin-server - Casbin as a Service (CaaS)
colfer - binary serialization format
go-mod-upgrade - Update outdated Go dependencies interactively
goprotobuf - Go support for Google's protocol buffers
depu - A tool to check available updates of packages in go.mod.
easyjson - Fast JSON serializer for golang.
go-mod-outdated - Find outdated dependencies of your Go projects. go-mod-outdated provides a table view of the go list -u -m -json all command which lists all dependencies of a Go project and their available minor and patch updates. It also provides a way to filter indirect dependencies and dependencies without updates.
mapstructure - Go library for decoding generic map values into native Go structures and vice versa.
kratos - Your ultimate Go microservices framework for the cloud-native era.
go-capnproto - Cap'n Proto library and parser for go. This is go-capnproto-1.0, and does not have rpc. See https://github.com/zombiezen/go-capnproto2 for 2.0 which has rpc and capabilities.