[Enhancement] Supports dynamic configuration for EventMesh SDK used by the source/sink worker
- 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.
### Enhancement Request
Currently the eventmesh sdk used in the source/sink worker defaults to the tcp client, which needs to support dynamic configuration to decide which client to use.
### Describe the solution you'd like
Currently the eventmesh sdk used in the source/sink worker defaults to the tcp client, which needs to support dynamic configuration to decide which client to use.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by tracing how the EventMesh SDK is used by the source and sink workers and where the default TCP client is selected. Identify the existing configuration path and the supported client choices before defining what dynamic selection should cover. Done means the workers can choose the client through configuration rather than always using the TCP client, with tests covering the selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100