Google Git
Sign in
apache / rocketmq-apis / 205e59cb0c427bb1f3d941a6c1b0b74322d62095
commit205e59cb0c427bb1f3d941a6c1b0b74322d62095[log] [tgz]
authorlk <xdkxlk@outlook.com>Wed May 24 17:50:30 2023 +0800
committerGitHub <noreply@github.com>Wed May 24 17:50:30 2023 +0800
treee057e943237fe08fcd1965cc137b1d1adc0631fc
parent8e27037035693cf5e3f0afa1e40e277b19ac0f1d [diff]
[ISSUE #80] Update document for pull-related RPC (#81)
1 file changed
tree: e057e943237fe08fcd1965cc137b1d1adc0631fc
  1. .github/
  2. apache/
  3. cpp/
  4. java/
  5. .asf.yaml
  6. .bazelrc
  7. .bazelversion
  8. .clang-format
  9. .gitignore
  10. BUILD.bazel
  11. ChangeLog.md
  12. compile.bzl
  13. deps.bzl
  14. LICENSE
  15. NOTICE
  16. plugin.bzl
  17. README.md
  18. StatusCode.md
  19. StyleGuide.md
  20. WORKSPACE
README.md

Overview

RocketMQ APIs use Protocol Buffers version 3 (proto3) as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. Reading these definitions can understand RocketMQ 5.0 models and API behaviors easily.

Currently, Apache RocketMQ only supports these APIs over gRPC, a high-performance binary RPC protocol over HTTP/2. The implementation consists of two parts:

  • rocketmq: The main repo of Apache RocketMQ contains a proxy module that implements this specification in the server-side.
  • rocketmq-clients: A mono repo consists of polyglot clients that implement this specification in the client-side.