[
https://issues.apache.org/jira/browse/TUBEMQ-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113867#comment-17113867
]
Guocheng Zhang commented on TUBEMQ-72:
--------------------------------------
After analyzing the implementation of Kafka, TubeMQ cannot directly apply
Kafka's protocol. The main reason is that kafka uses a decentralized server
model, while TubeMQ has central nodes, and the related management and control
information is isolated in the Broker
However, we will implement similar operations in the future, such as providing
a similar operation interface on the central nodes of TubeMQ, and completing
the access of different MQ protocols through the Proxy node of TubeMQ.
> Support Kafka Compatible Protocol in TubeMQ
> -------------------------------------------
>
> Key: TUBEMQ-72
> URL: https://issues.apache.org/jira/browse/TUBEMQ-72
> Project: Apache TubeMQ
> Issue Type: New Feature
> Reporter: Junping Du
> Priority: Major
>
> The Kafka protocol is general used in MQ area, and Apache Pulsar (another MQ)
> did work to support it. TubeMQ should do the same thing - given there are
> only six core client requests APIs.
> *Metadata* - Describes the currently available brokers, their host and port
> information, and gives information about which broker hosts which partitions.
> *Send* - Send messages to a broker
> *Fetch* - Fetch messages from a broker, one which fetches data, one which
> gets cluster metadata, and one which gets offset information about a topic.
> *Offsets* - Get information about the available offsets for a given topic
> partition.
> *Offset Commit* - Commit a set of offsets for a consumer group
> *Offset Fetch* - Fetch a set of offsets for a consumer group
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
