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
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
JIRA link - [INLONG-72] created by junping_du