[Question]creating too many RocketMQ connections
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Question
A project will have many consumer groups, which will create a lot of clients (including pubs and subs), as well as many ClientGroupWrappers, producers (can they be shared?), consumers, and broadcasts (why do they need to be created? I don't need to);
Contributor guide
Research direction
The issue names clients, ClientGroupWrappers, producers, consumers, and broadcasts but no files or tests. Start by tracing where these components are created and connected, then clarify with maintainers which resources may be shared and whether broadcasts are required. Done would require an agreed connection lifecycle and corresponding implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100