proposal
gRPC
proposal | gRPC | |
---|---|---|
5 | 201 | |
697 | 40,775 | |
2.3% | 0.6% | |
7.5 | 9.9 | |
4 days ago | 5 days ago | |
C++ | ||
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
-
Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle.
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.
See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...
The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.
-
Delving Deeper: Enriching Microservices with Golang with CloudWeGo
While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future.
-
gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .
-
Dart on the Server: Exploring Server-Side Dart Technologies in 2024
The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.
- Usando Spring Boot RestClient
-
How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide
gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming.
-
Actual SSH over HTTPS
In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1].
This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing.
There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing.
I expect that in the future most communications will be over encrypted HTTP2 and QUIC simply because middleware creators can not resist to discriminate.
[1] <https://grpc.io>
-
Why gRPC is not natively supported by Browsers
Even in the https://grpc.io blog says this
-
SGSG (Svelte + Go + SQLite + gRPC) - open source application
gRPC
What are some alternatives?
ngx-grpc - Angular gRPC framework
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
kill-zscaler - Kill Zscaler without password or jail Zscaler in a virtual machine
Apache Thrift - Apache Thrift
HTTP Parser - http request/response parser for c
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
membrane_core - The core of the Membrane Framework, advanced multimedia processing framework
zeroRPC - zerorpc for python
pixie - Instant Kubernetes-Native Application Observability
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
re - Recursive search and replace tool
nanomsg - nanomsg library