apache / apache/rocketmq

[Enhancement] proxy local mode support lite message

Open
#10,478 2 comments 0 reactions 0 assignees View on GitHub
type/enhancement
Dominant language
Java
Stars
22.6k
Forks
12k
Avg merge
3d 1h
Merged PRs (30d)
27

Description

### Before Creating the Enhancement Request

- [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

### Summary

Proxy local mode support Lite message.

### Motivation

In the current Apache RocketMQ 5.x architecture, the Proxy component supports two deployment modes: Cluster mode and Local mode.

Cluster Mode: Broker and Proxy are deployed separately, with full functionality including gRPC protocol support and Lite message processing capabilities.

Local Mode: Broker and Proxy run in the same JVM process (using --enable-proxy flag). This mode is simple to deploy, resource-efficient, and typically used for development/testing or edge nodes.

In RocketMQ 5.5.0, the community introduced Lite Mode (based on RIP-83), designed for AI scenarios and high-volume conversations (e.g., Agent communication). It features low resource consumption, event-driven dispatch, and broker-side state persistence. However, after testing and source code analysis, Local Mode currently does NOT support Lite Message processing or subscription mechanisms.

### Describe the Solution You'd Like

Support lite methods in LocalMessageService and LocalServiceManager

### Describe Alternatives You've Considered

no alternatives

### Additional Context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with LocalMessageService and LocalServiceManager, then trace how Proxy Local mode is wired when --enable-proxy is used. Compare those paths with the existing Cluster-mode Lite message processing and subscription behavior. Done means Local mode supports the Lite methods and subscription mechanisms described in the issue, with verification in the project's relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.