The Wayback Machine - https://web.archive.org/web/20201110095308/https://github.com/topics/grpc
Skip to content
#

gRPC

grpc logo

gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services.

Here are 3,193 public repositories matching this topic...

grpc-gateway

Surging is a micro-service engine that provides a lightweight, high-performance, modular RPC request pipeline. The service engine supports http, TCP, WS,Grpc, Thrift,Mqtt, UDP, and DNS protocols. It uses ZooKeeper and Consul as a registry, and integrates it. Hash, random, polling, Fair Polling as a load balancing algorithm, built-in service governance to ensure reliable RPC communication, the engine contains Diagnostic, link tracking for protocol and middleware calls, and integration SkyWalking Distributed APM
  • Updated Aug 9, 2020
  • C#
armeria
ikhoon
ikhoon commented Mar 19, 2020

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

fortio
mandarjog
mandarjog commented May 15, 2019

At present we can run the load generator for a set amount of time or a certain number of requests.
I would like to a mode --reconnetRequests=1000 where fortio client will reconnect after 1000 requests.

Use case: We are testing SDS cert rotation using an https fortio client (std client).
For cert rotation to be exercised fortio should reconnect periodically to fetch the new cert.
In

Zelldon
Zelldon commented Nov 5, 2020

Is your feature request related to a problem? Please describe.

Currently in the java client we need to write:

  client.newCompleteCommand(job.getKey()).send();

For me it is annoying to always write .getKey(). It should be clear that I want to complete that job the client can handle that also internally.

Describe the solution you'd like

I suggest that we overl

Created by Google

Released August 2016

Latest release 14 days ago

Repository
grpc/grpc
Website
grpc.io
Wikipedia
Wikipedia
You can’t perform that action at this time.