awesome-grpc
gRPC
awesome-grpc | gRPC | |
---|---|---|
4 | 206 | |
7,340 | 40,982 | |
1.2% | 0.6% | |
5.8 | 9.9 | |
about 1 month ago | 5 days ago | |
C++ | ||
Creative Commons Attribution 4.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.
awesome-grpc
- What, in your opinion, are some interesting programming projects written using gRPC?
-
gRPC test-and-try with Akka Serverless and Evans
Definitely check out Awesome gRPC for tons of great resources, even beyond the tooling like the Evans CLI. Also, if you want to start building gRPC services in a streamlined fashion, without spinning up servers and figuring out deploys and operations, then you should sign-up for an account at Akka Serverless.
-
Everything about APIs
Awesome gRPC
-
Any options to test gRPC endpoints?
There are many options, this awesome list has great summary, i was just wondering if theres a tool inside IntelliJ
gRPC
-
Navigating the gRPC Galaxy: A Different view into Efficient 'api to api' Communication
official gRPC link
-
Best Practices for Building Microservices with NestJS
Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs.
-
Why Did Google Choose To Implement gRPC Using HTTP/2?
gRPC is an open-source high-performance RPC framework developed by Google. The design goal of gRPC is to run in any environment, supporting pluggable load balancing, tracing, health checking, and authentication. It not only supports service calls within and across data centers but is also suitable for the last mile of distributed computing, connecting devices, mobile applications, and browsers to backend services. For more on the motivation and principles behind gRPC's design, refer to this article: gRPC Motivation and Design Principles.
-
Difference between GraphQL, REST, and gRPC
And, gRPC is a high-performance, open-source protocol used for creating APIs. It uses Google's Protocol Buffers as a data format and provides support for streaming and bi-directional communication.
-
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
What are some alternatives?
public-apis - A collective list of free APIs
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
websocket-client - WebSocket client for Python
Apache Thrift - Apache Thrift
api-guidelines - Microsoft REST API Guidelines
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
insomnia - The open-source, cross-platform API client for GraphQL, REST, WebSockets, SSE and gRPC. With Cloud, Local and Git storage.
zeroRPC - zerorpc for python
awesome-rest - A collaborative list of great resources about RESTful API architecture, development, test, and performance
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
awesome-json-rpc - Curated list of JSON-RPC resources.
nanomsg - nanomsg library