Google Git
Sign in
apache / rocketmq-apis / refs/heads/zhimin/fix-bazel2
commit332f2c541251f53d3164bd485c43d020b451b4bd[log] [tgz]
authorlizhimins <707364882@qq.com>Tue Oct 14 19:15:31 2025 +0800
committerlizhimins <707364882@qq.com>Tue Oct 14 19:15:31 2025 +0800
treef5666b567aeaabb27d423e838b27ca8e8dc13d3d
parent5c9f84199bffa79b2ed73beb37774ca92e749c19 [diff]
build(bazel): Compile using the specified versions of GCC and G++

Change-Id: I906eee7be5ad3804163b606b3fec702c09b0e003
3 files changed
tree: f5666b567aeaabb27d423e838b27ca8e8dc13d3d
  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.