rocketmq-rust

Welcome to Apache Rocketmq Rust implementation (Unofficial ). RocketMQ-Rust is a reimplementation of the Apache RocketMQ message middleware in the Rust language. This project aims to provide Rust developers with a high-performance and reliable message queue service, making full use of the features of the Rust language.

RocketMQ-Rust Features

Rust Language Advantages: Leveraging the benefits of Rust, such as memory safety, zero-cost abstractions, and high concurrency performance, RocketMQ-Rust offers an efficient and reliable message middleware.
Asynchronous and Non-blocking Design: RocketMQ-Rust takes full advantage of Rust's asynchronous programming capabilities, adopting a non-blocking design that supports high-concurrency message processing.
Ecosystem Integration: As part of the Rust ecosystem, RocketMQ-Rust integrates well with other libraries and frameworks within the Rust ecosystem, providing flexible integration options for developers.
Cross-platform Support: RocketMQ-Rust supports multiple platforms, including Linux, Windows, macOS, making it convenient for use in different environments.

Getting Started

Requirements

rust toolchain MSRV is 1.75.(stable,nightly)

Run name server

Run the following command to see usage：

windows platform

cargo run --bin rocketmq-namesrv-rust -- --help

RocketMQ Name server(Rust)

Usage: rocketmq-namesrv-rust.exe [OPTIONS]

Options:
  -p, --port <PORT>  rocketmq name server port [default: 9876]
  -i, --ip <IP>      rocketmq name server ip [default: 127.0.0.1]
  -h, --help         Print help
  -V, --version      Print version

Linux platform

$ cargo run --bin rocketmq-namesrv-rust -- --help

RocketMQ Name server(Rust)

Usage: rocketmq-namesrv-rust [OPTIONS]

Options:
  -p, --port <PORT>  rocketmq name server port [default: 9876]
  -i, --ip <IP>      rocketmq name server ip [default: 127.0.0.1]
  -h, --help         Print help
  -V, --version      Print version

Run the following command to start the name server

cargo run --bin rocketmq-namesrv-rust

Modules

The existing RocketMQ has the following functional modules:

Name Server
Broker
Store (Local Storage)
Controller (High Availability)
Client (SDK)
Proxy
Tiered Store (Tiered Storage Module)

The specific functions of each module can be referred to in the official RocketMQ documentation. The Rust implementation will be carried out sequentially in the following order.

Name Server

Feature list:

Not support: 💔 ❌

Base support: ❤️ ✅

Perfect support: 💖 ✅

Feature	request code	Support
Put KV Config	100	💖 ✅
Get KV Config	101	💖 ✅
Delete KV Config	102	💖 ✅
Get kv list by namespace	219	💖 ✅
Query Data Version	322	💖 ✅
Register Broker	103	💖 ✅
Unregister Broker	104	💖 ✅
Broker Heartbeat	904	💖 ✅
Get broker member_group	901	💖 ✅
Get broker cluster info	106	💖 ✅
Wipe write perm of boker	205	💖 ✅
Add write perm of brober	327	💖 ✅
Get all topic list from name server	206	💖 ✅
Delete topic in name server	216	💖 ✅
Register topic in name server	217	💖 ✅
Get topics by cluster	224	💖 ✅
Get system topic list from name server	304	💖 ✅
Get unit topic list	311	💖 ✅
Get has unit sub topic list	312	💖 ✅
Get has unit sub ununit topic list	313	💖 ✅
Update name server config	318	💔 ❌
Get name server config	318	💔 ❌

Other module implementations will be done subsequently, starting with the Rust implementation of the Name Server. The goal is to achieve functionality similar to the Java version.

Contributing

Contributions to code, issue reporting, and suggestions are welcome. The development of RocketMQ-Rust relies on the support of developers. Let's collaborate to advance Rust in the message middleware domain.

Stargazers Over Time	Contributors Over Time

License

RocketMQ-Rust is licensed under the Apache License 2.0 and MIT license

mahonelau/rocketmq-rust