mxsm opened a new issue, #3192: URL: https://github.com/apache/incubator-eventmesh/issues/3192
### 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 The current project has an eventmesh-admin module, and according to the documentation, its main function is to manage clients, topics, and subscriptions. Based on my understanding, the implementation of client management, topic (CRUD), and subscription should all be located in this module. However, in practice, the related functions are implemented in the sub-modules of the eventmesh-connector-plugin module. For example, in the singleton pattern, topic creation is implemented in the eventmesh-connector-standalone module instead of the corresponding sub-module in the eventmesh-admin module. I would like to know what the current code module plan is. For example, should the implementation of topic creation related functions for RocketMQ be located in the eventmesh-admin-rocketmq module? @jonyangx @xwm1992 @qqeasonchen Are there any relevant agreements in the current project? As I mentioned before, I plan to refactor the admin-related code in the eventmesh-connector-plugin into the corresponding sub-module in the eventmesh-admin module. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
