apache / apache/rocketmq-clients
Golang: Make each 'Client' have an independent 'ClientManager'
- Dominant language
- Java
- Stars
- 505
- Forks
- 313
- Avg merge
- 11h 28m
- Merged PRs (30d)
- 6
Description
Currently a process globally shares a 'ClientManager', so only one 'Conn' is established for each endpoint. When users create a new client, their expectations should be completely independent.

Contributor guide
No contributing guide indexed for this repository
Research direction
Read the Golang Client and ClientManager implementation first, tracing where the process-wide manager and endpoint connections are created. Verify how multiple clients currently share a Conn, then make independence observable by ensuring each Client can establish and manage its own connection for the same endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100