Name
Last commit
Last update
.github Update stale.yml
bazel bazel build support glog
cmake Fix incorrect cmake required version
docs add pprof support in macos
example Merge branch 'master' into cmake_support
java Add empty folder of python and java
python Add empty folder of python and java
src Put Impl of get_clocktime into butil/time.cpp
test Put Impl of get_clocktime into butil/time.cpp
tools Put Impl of get_clocktime into butil/time.cpp
.gitignore support conditional flags on certain gcc and compile proto file using cmake, based on CMakefile from kevin-xu-158
.travis.yml Find core files and print stack if build failed
BUILD bazel support example and unittest
CMakeLists.txt Put Impl of get_clocktime into butil/time.cpp
Dockerfile add docker
LICENSE Patch svn r35206 & fix compilation of tools
Makefile Add NDEBUG
README.md Add tutorial_on_building_services.pptx
README_cn.md Add tutorial_on_building_services.pptx
WORKSPACE travis-ci support bazel build
build_in_travis_ci.sh keep only one bazel compilation combination in travis
config.h.in support conditional flags on certain gcc and compile proto file using cmake, based on CMakefile from kevin-xu-158
config_brpc.sh add missing files for MAC
glog.BUILD bazel build support glog
leveldb.BUILD add workspace.bzl and bazel.rc

中文版

Build Status

brpc

A industrial-grade RPC framework used throughout Baidu, with 1,000,000+ instances(not counting clients) and thousands kinds of services, called "baidu-rpc" inside Baidu. Only C++ implementation is opensourced right now.

You can use it to:

Try it!

Contribute code

If you can fix any of the issues or add new features, you're welcome to send the PR to us. If the PR is accepted, your contribution will be scored from 0 to 5 points according to the difficulty and quality (higher is better). If you accumulate 10 points, you can contact us for interviewing opportunities or recommendation letter for your future jobs.

Make sure your code meets following requirements before submitting the PR:

  • The code conforms to google C++ coding style and is indented by 4 spaces.
  • The code appears where it should be. For example the code to support an extra protocol should not be put in general classes like server.cpp, channel.cpp, while a general modification would better not be hidden inside a very specific protocol.
  • Has unittests.

Check following items after submitting the PR:

  • Compilations and unittests in travis-ci are passed.