apache / apache/rocketmq-externals

[KEPLER-MISSION] Apache RocketMQ 6.0 subtasks - native mqtt support

Open
#669 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
4.6k
Forks
3k
Avg merge
2h 33m
Merged PRs (30d)
1

Description

**FEATURE REQUEST**

1. Please describe the feature you are requesting.
Add store plugin of RocketMQ.
![image](https://user-images.githubusercontent.com/3734319/104177355-94beb400-5443-11eb-8014-70f189bab2a0.png)
2. Provide any additional detail on your proposed use case for this feature.
- In our company, there are a lot of IOT devices cases. These devices use MQTT protocol and have high availability need for message service.
To support high availability and scalability, the metadata and data now stored in memory is not enough. A storage plugin of RocketMQ seems necessary.
- Except the consume of MQTT message for IOT devices, we cloud consume message from RocketMQ for data calculate and analyze.
3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
【blocker】
4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

- [x] Support metadata storage of RocketMQ
- [x] Support message storage of RocketMQ

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the requested RocketMQ store plugin scope and the checked metadata-storage and message-storage subtasks. Inspect linked pull request #687 for prior implementation context; done means providing persistent, scalable storage for both metadata and messages while supporting the stated MQTT use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.