[
https://issues.apache.org/jira/browse/TUBEMQ-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141688#comment-17141688
]
Cunzhou Tang commented on TUBEMQ-25:
------------------------------------
Hi [~gosonzhang] ,
The Go SDK plan is as follows:
1. TubeMQ Consumer (preferential support for pull consumption)
2. TubeMQ Producer (supports synchronous production and asynchronous production)
3. Connection pool implementation (connection multiplexing, automatic
reconnection of broken links, automatic recovery of idle connections, sharing
according to sessionFactory)
4. Rate limiter & control the amount of data consumed by consumers per unit time
5. Authentication & prevent production and consumption around the Master
6. TLS
7. Precisely specify the offset partition consumption
8. Frequency control
9. Effectively-Once
10. Inactivity beyond specified minutes, mainly at the production end, such as
3 minutes
11. A single group consumes multiple Topic consumption + server filter
consumption
12. Automatically shield the dead pixels, detect the dead pixels through the
algorithm, and automatically shield the fault Broker's data transmission
It takes about 3-4 persons
One person is responsible for consumption and production news, including but
not limited to:
- Consumer messages (pull & push)
- Production messages
One person is responsible for connection pool implementation, including but not
limited to:
- Connection multiplexing
- Automatic reconnection of broken chain
- Automatic recovery of idle connections
- Shared by sessionFactory
One person is responsible for authentication and authentication, including but
not limited to:
- Authentication
- TLS
- Prevent production and consumption around the Master
One person is responsible for frequency control and stability, including but
not limited to:
- Frequency control
- Effectively-Once
- Inactive for more than specified minutes
- Single Topic Consumption Multiple Topic Consumption + Server Filter
Consumption
- Automatically shield the dead pixels, detect the dead pixels through the
algorithm, and automatically shield the fault Broker's data transmission.
I will first give consumers of the pull version recently, others can develop
the rest of the functions based on my code.
> Go SDK support for TubeMQ
> -------------------------
>
> Key: TUBEMQ-25
> URL: https://issues.apache.org/jira/browse/TUBEMQ-25
> Project: Apache TubeMQ
> Issue Type: New Feature
> Reporter: Guocheng Zhang
> Assignee: Cunzhou Tang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
