YMJake.RocketMQ.Client 5.3.8

RocketMQ C# Client with FIFO Accelerator

Enhanced C# client for Apache RocketMQ 5.x with full feature support and FIFO Consume Accelerator.

Features

All official RocketMQ 5.x C# features are fully implemented:

• ✅ Producer with standard messages
• ✅ Producer with FIFO messages
• ✅ Producer with timed/delay messages
• ✅ Producer with transactional messages
• ✅ Producer with recalling timed/delay messages
• ✅ Simple consumer (pull mode with Receive())
• ✅ Push consumer with concurrent message listener
• ✅ Push consumer with FIFO message listener
• ✅ Lite push consumer with dynamic subscription
• ✅ Lite simple consumer with lite topic subscription
• ✅ Push consumer with FIFO consume accelerator (Enhanced feature)
• ✅ Message filtering with Tag and SQL92 expressions (v5.2.8)
• ✅ Priority Message (v5.3.4)

Supports .NET 8.0 (LTS) and .NET 10.0

Installation

dotnet add package YMJake.RocketMQ.Client

Optional: OpenTelemetry Instrumentation

dotnet add package YMJake.RocketMQ.Client.OpenTelemetry

Automatic distributed tracing and metrics support with W3C Trace Context propagation. See package docs for details. The core YMJake.RocketMQ.Client package now stays lean and does not carry OpenTelemetry metrics/exporter dependencies; tracing and metrics live in the optional OpenTelemetry package.

OpenTelemetry SemConv Alignment

The OpenTelemetry package is aligned with RocketMQ's messaging semantic conventions at the client side:

• Standard messaging attributes such as messaging.system, messaging.operation.name, messaging.operation.type, and messaging.destination.name
• RocketMQ-specific attributes such as messaging.consumer.group.name, messaging.rocketmq.namespace, messaging.rocketmq.message.type, messaging.rocketmq.message.tag, messaging.rocketmq.message.group, messaging.rocketmq.message.keys, and messaging.rocketmq.message.delivery_timestamp
• Client-side metrics for send, delivery, await, and process latency

The implementation intentionally avoids broker-side metrics and labels such as cluster or broker node identifiers. If the core client later exposes stable endpoint/error details in diagnostics, we can optionally extend the instrumentation with additional fields such as server.address, server.port, and error.type.

Examples

See RocketMQ.Client.Examples for sample code.

For a runnable WebAPI demo that exercises tracing with OpenTelemetry, see RocketMQ.Client.OpenTelemetry.Sample.

Java Parity Status

This project is largely aligned with the latest Java client on core messaging paths.

Aligned

• OffsetOption for Lite Push Consumer
• Priority Message support (build/send/parse/message type mapping)
• FIFO message-group load balancing with SipHash24
• Push FIFO consume accelerator (parallel by message group, ordered within group)
• LiteSimpleConsumer with lite topic management and lite client type
• Session.SyncSettings concurrent synchronization
• Push ACK / ChangeInvisible / DLQ main behavior and logging paths, including lite-topic propagation for ack and change-invisible flows
• Message filtering with Tag and SQL92 expressions + interceptor filtering flow

Ongoing Parity Improvements

• OpenTelemetry tracing and metrics detail alignment
• Minor edge-case log wording and exception-path consistency
• Builder default/config parity verification across languages

License

Apache License 2.0. Based on Apache RocketMQ Clients.

Packages

• Main Client: YMJake.RocketMQ.Client
• OpenTelemetry: YMJake.RocketMQ.Client.OpenTelemetry
• Repository: Gitee