proposal
grpc-proto
| proposal | grpc-proto | |
|---|---|---|
| 5 | 1 | |
| 697 | 235 | |
| 2.3% | 1.7% | |
| 7.5 | 6.6 | |
| 3 days ago | 7 days ago | |
| Starlark | ||
| Apache License 2.0 | Apache License 2.0 |
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.
proposal
- gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
- Why HTTP/3 is eating the world
-
eBPF will help solve service mesh by getting rid of sidecars
Not convinced that this a better solution then just implementing most of these features as part of the protocol. Most languages already support grpc load balancing.
https://github.com/grpc/proposal/blob/master/A27-xds-global-...
-
Why gRPC for microservices communication?
The future of gRPC load balancing is proxy less using the xDS APIs of Envoy. More info here. But as of now, there is no straightforward solution since there are no xDS management servers supporting this unless you are on GKE where you can use Traffic Director. Istio has experimental support, and it is said that it works, but it might require some manual configuration. If Go is fine for you, you could also be using go-control-plane, but definitely, the ecosystem around gRPC and xDS does not seem to be mature enough.
- Why Load Balancing Grpc Is Tricky
grpc-proto
-
gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
The State which was returned by the name resolver in the previous steps contains both a list of endpoints and a configuration called ServiceConfig. One of the main use cases of the ServiceConfig is to decide which load balancing policy to go for (e.g. round_robin). ServiceConfig is based on a proto message but the name resolver returns it in JSON form. Let’s look at an example ServiceConfig:
What are some alternatives?
ngx-grpc - Angular gRPC framework
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
kill-zscaler - Kill Zscaler without password or jail Zscaler in a virtual machine
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
HTTP Parser - http request/response parser for c
grpc-kuber-load-balancing - gRPC Name Resolution and Load Balancing on Kubernetes
membrane_core - The core of the Membrane Framework, advanced multimedia processing framework
pixie - Instant Kubernetes-Native Application Observability
re - Recursive search and replace tool
natter - [EXPERIMENTAL] A peer-to-peer TCP port forwarding library using NAT traversal with QUIC
grpc-web - gRPC for Web Clients
erde - Geospatial python toolkit: common functions, easy CLI creation, dataframes streams