yuanzhongqiao/rocketmq

This system is a distributed message queue platform that manages message storage, routing, and delivery through a broker and controller architecture. It provides comprehensive client-side APIs for producing and consuming messages, supporting patterns such as transactional messaging, ordered delivery, and high-performance POP consumption. The system also features a proxy layer for gRPC and remoting protocols, enabling flexible integration and cluster management.

This period focused on significantly expanding the RocketMQ broker and client capabilities, introducing new consumption modes like POP and LitePull, and enhancing broker features such as cold read control, transaction tracking, and persistent storage via RocksDB. The client library was also modernized with new APIs, hooks, and fault tolerance mechanisms, while the build system was upgraded to support Bazel alongside Maven.

53 changes

This period focused on implementing core security and observability features, specifically introducing Access Control List (ACL) support, SQL92 message filtering, and comprehensive message tracing with OpenTracing integration. The work also included significant expansion of unit test coverage across the client, broker, and filter modules to ensure the stability of these new capabilities.

55 changes

This period focused on introducing the Controller module for high-availability broker management and building a comprehensive gRPC v2 Proxy layer. The work established a new service-oriented architecture for the proxy, supporting features like request-response, scheduled messages, and transactional messaging via both gRPC and remoting protocols.

75 changes

This period focused on introducing new capabilities for tiered storage and message receipt handling, alongside enhanced observability through OpenTelemetry metrics. The work also included significant test coverage for the new components and access control mechanisms.

7 changes

yuanzhongqiao/rocketmq was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.