-
Notifications
You must be signed in to change notification settings - Fork 11.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RIP-28]Support light message queue (LMQ) multi-consumeQueue atomic dispatch #3666
Comments
It seems to be a considerable change. I suggest you open a new RIP to introduce your design. You can refer to wiki-rip. |
I could not figure out what you want to do from your description. You could arrange your sentences. |
Some messaging scenarios require light message queue, Such as MQTT multi-level topic or AMQP lightweight queue can be set at will by users when sending and subscription message. Therefore, the implementation of LMQ's queue model is required |
Looking forward to it very much. We have a big demand scenario here. |
Merged |
Co-authored-by: hening <ninghe.hn@alibaba-inc.com>
This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs. |
This issue was closed because it has been inactive for 3 days since being marked as stale. |
Some messaging scenarios require Light message queue to support a large number of topics, such as MQTT, AMQP protocol, its multi-level topic sending and subscription can be set at will, and the number of multi-level topics is very large, the original RocketMQ topic It is resource-heavy, and it is difficult to support millions or more of lightweight multi-level topics.
Let's define Light message queue as (LMQ)
Light message queue (LMQ) needs to implement multi-dimensional dispatch of a message based on ConsumeQueue, and a message can support multiple lightweight queue consumption。
Light message queue (LMQ) needs to implement multi-level topic management, so topic metadata also needs adaptation management, such as topic verification, data cleaning and so on.
Light message queue (LMQ) needs to implement lightweight queue consumption offset management
The text was updated successfully, but these errors were encountered: