The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
ncteisen f935ab4141 Fix include guard sanity 7 years ago
.github Add me to build system owners 7 years ago
.vscode Adding shim for debugging node tests using vscode. 8 years ago
bazel Merge pull request #13993 from vjpai/buildown 7 years ago
cmake improve comments on find_package(Protobuf) 7 years ago
doc Bump version to 1.10 7 years ago
etc minor fix 7 years ago
examples fix protobuf usage in the example 7 years ago
include Merge branch 'master' of https://github.com/grpc/grpc into channel-tracing 7 years ago
src Fix include guard sanity 7 years ago
summerofcode 2018 ideas (gRPC Python Team's, at least) 7 years ago
templates PHP: make generate_projects.sh smarter for package.xml 7 years ago
test Merge branch 'master' of https://github.com/grpc/grpc into channel-tracing 7 years ago
third_party Use rake-compiler-dock's Dockerfile as a base in grpc's fork of it 7 years ago
tools Move object registry out of gpr 7 years ago
vsprojects Merge branch 'master' of github.com:grpc/grpc into filters_prio 7 years ago
.clang-format Update clang-format to 5.0 7 years ago
.clang_complete Enable clang-tidy as a sanity check, fix up all known failures 7 years ago
.editorconfig Adding an editorconfig configuration file. 10 years ago
.gitignore cmake output to gitignore 7 years ago
.gitmodules Fetch boringssl-with-bazel submodule from GitHub 7 years ago
.istanbul.yml Moved gRPC node package root to repo root, made it depend on grpc.gyp 9 years ago
.pylintrc gRPC Python test infrastructure 7 years ago
.rspec Bundled C core with Ruby library 9 years ago
.travis.yml Have Travis build the Sample app with frameworks too 9 years ago
.yardopts Adding a .yardopts file at the root so rubydocs isn't getting lost. 9 years ago
AUTHORS change LICENSE, add AUTHORS 8 years ago
BUILD Move object registry out of gpr 7 years ago
CMakeLists.txt Move object registry out of gpr 7 years ago
CODE-OF-CONDUCT.md Fix code of conduct 8 years ago
CONTRIBUTING.md Update CONTRIBUTING.md 7 years ago
Gemfile Bundled C core with Ruby library 9 years ago
INSTALL.md address comments 7 years ago
LICENSE fix license file 8 years ago
MANIFEST.md Remove tox 9 years ago
Makefile Move object registry out of gpr 7 years ago
NOTICE.txt change LICENSE, add AUTHORS 8 years ago
OWNERS Substitute a11r for ctiller in all OWNERS files 7 years ago
PYTHON-MANIFEST.in Changes 8 years ago
README.md Update README.md Copyright Notice 7 years ago
Rakefile Use rake-compiler-dock's Dockerfile as a base in grpc's fork of it 7 years ago
WORKSPACE Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build. 7 years ago
build.yaml Move object registry out of gpr 7 years ago
build_config.rb Decouple alarm construction from setting to avoid races in MT code 7 years ago
composer.json Use https://grpc.io consistently as the canonical URL 8 years ago
config.m4 Move object registry out of gpr 7 years ago
config.w32 Move object registry out of gpr 7 years ago
gRPC-Core.podspec Move object registry out of gpr 7 years ago
gRPC-ProtoRPC.podspec Regenerate projects 7 years ago
gRPC-RxLibrary.podspec Regenerate projects 7 years ago
gRPC.podspec Regenerate projects 7 years ago
grpc.bzl fix remaining license notices 8 years ago
grpc.def Move histogram to test/core/util 7 years ago
grpc.gemspec Move object registry out of gpr 7 years ago
grpc.gyp Move object registry out of gpr 7 years ago
package.xml Move object registry out of gpr 7 years ago
requirements.txt Update Python dependency to protobuf v3.5.0.post1 7 years ago
setup.cfg Enable running Python formatting 8 years ago
setup.py Allow compiling grpc without use of pthread_atfork 7 years ago

README.md

Build Status

gRPC - An RPC library and framework

Join the chat at https://gitter.im/grpc/grpc

Copyright 2015 The gRPC Authors

Documentation

You can find more detailed documentation and examples in the doc and examples directories respectively.

Installation & Testing

See INSTALL for installation instructions for various platforms.

See tools/run_tests for more guidance on how to run various test suites (e.g. unit tests, interop tests, benchmarks)

See Performance dashboard for the performance numbers for the latest released version.

Repository Structure & Status

This repository contains source code for gRPC libraries for multiple languages written on top of shared C core library src/core.

Libraries in different languages may be in different states of development. We are seeking contributions for all of these libraries.

Language Source
Shared C [core library] src/core
C++ src/cpp
Ruby src/ruby
Python src/python
PHP src/php
C# src/csharp
Objective-C src/objective-c

Java source code is in the grpc-java repository. Go source code is in the grpc-go repository. NodeJS source code is in the grpc-node repository.

See MANIFEST.md for a listing of top-level items in the repository.

Overview

Remote Procedure Calls (RPCs) provide a useful abstraction for building distributed applications and services. The libraries in this repository provide a concrete implementation of the gRPC protocol, layered over HTTP/2. These libraries enable communication between clients and servers using any combination of the supported languages.

Interface

Developers using gRPC typically start with the description of an RPC service (a collection of methods), and generate client and server side interfaces which they use on the client-side and implement on the server side.

By default, gRPC uses Protocol Buffers as the Interface Definition Language (IDL) for describing both the service interface and the structure of the payload messages. It is possible to use other alternatives if desired.

Surface API

Starting from an interface definition in a .proto file, gRPC provides Protocol Compiler plugins that generate Client- and Server-side APIs. gRPC users typically call into these APIs on the Client side and implement the corresponding API on the server side.

Synchronous vs. asynchronous

Synchronous RPC calls, that block until a response arrives from the server, are the closest approximation to the abstraction of a procedure call that RPC aspires to.

On the other hand, networks are inherently asynchronous and in many scenarios, it is desirable to have the ability to start RPCs without blocking the current thread.

The gRPC programming surface in most languages comes in both synchronous and asynchronous flavors.

Streaming

gRPC supports streaming semantics, where either the client or the server (or both) send a stream of messages on a single RPC call. The most general case is Bidirectional Streaming where a single gRPC call establishes a stream where both the client and the server can send a stream of messages to each other. The streamed messages are delivered in the order they were sent.

Protocol

The gRPC protocol specifies the abstract requirements for communication between clients and servers. A concrete embedding over HTTP/2 completes the picture by fleshing out the details of each of the required operations.

Abstract gRPC protocol

A gRPC RPC comprises of a bidirectional stream of messages, initiated by the client. In the client-to-server direction, this stream begins with a mandatory Call Header, followed by optional Initial-Metadata, followed by zero or more Payload Messages. The server-to-client direction contains an optional Initial-Metadata, followed by zero or more Payload Messages terminated with a mandatory Status and optional Status-Metadata (a.k.a.,Trailing-Metadata).

Implementation over HTTP/2

The abstract protocol defined above is implemented over HTTP/2. gRPC bidirectional streams are mapped to HTTP/2 streams. The contents of Call Header and Initial Metadata are sent as HTTP/2 headers and subject to HPACK compression. Payload Messages are serialized into a byte stream of length prefixed gRPC frames which are then fragmented into HTTP/2 frames at the sender and reassembled at the receiver. Status and Trailing-Metadata are sent as HTTP/2 trailing headers (a.k.a., trailers).

Flow Control

gRPC inherits the flow control mechanisms in HTTP/2 and uses them to enable fine-grained control of the amount of memory used for buffering in-flight messages.